Skip to content

Removing magic number from mem_block_header_t #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

ruben-ayrapetyan
Copy link
Contributor

No description provided.

JerryScript-DCO-1.0-Signed-off-by: Ruben Ayrapetyan r.ayrapetyan@samsung.com
@ruben-ayrapetyan ruben-ayrapetyan force-pushed the Ruben-remove-magic_num-from-heap-block-header branch from f2156ef to 593b1d7 Compare May 13, 2015 19:21
@ruben-ayrapetyan ruben-ayrapetyan added normal memory management Related to memory management or garbage collection development Feature implementation labels May 13, 2015
@ruben-ayrapetyan ruben-ayrapetyan added this to the Core ECMA features milestone May 13, 2015
@ruben-ayrapetyan ruben-ayrapetyan merged commit 593b1d7 into master May 13, 2015
@ruben-ayrapetyan ruben-ayrapetyan deleted the Ruben-remove-magic_num-from-heap-block-header branch May 13, 2015 19:39
* false - otherwise
*/
static bool
mem_is_block_free (const mem_block_header_t *block_header_p) /**< block header */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be marked as always inline?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose that this small function would be always inlined by compiler automatically.
If not, we would add the always_inline during optimization stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Feature implementation memory management Related to memory management or garbage collection normal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants