Skip to content
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

Modifty Metronome.hpp for moving into OMR #5064

Merged
merged 1 commit into from
Mar 13, 2019

Conversation

jason-hall
Copy link
Contributor

Signed-off-by: Jason Hall jasonhal@ca.ibm.com

Signed-off-by: Jason Hall <jasonhal@ca.ibm.com>
@dmitripivkine dmitripivkine self-assigned this Mar 12, 2019
@dmitripivkine dmitripivkine self-requested a review March 12, 2019 18:12

#include <assert.h>
#define ASSERT_LEVEL 0
#define assert1(expr) assert((ASSERT_LEVEL < 1) || (expr));
#define assert2(expr) assert((ASSERT_LEVEL < 2) || (expr));

#define MAX_UINT ((UDATA) (-1))
#define MAX_UINT ((uintptr_t) (-1))
Copy link
Contributor

Choose a reason for hiding this comment

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

This definition exists in OMR code already in AllocationContextSegregated.cpp
Also OMR has UDATA_MAX definition for this used widely.
Also there are multiple places in the code with ((uintptr_t) (-1)) and ((UDATA) (-1))
@charliegracie I wondering may be it is time to do cleanup and use single proper definition everywhere (done by two separate PRs - one for OMR another for OpenJ9) ?

@dmitripivkine dmitripivkine merged commit fe31337 into eclipse-openj9:master Mar 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants