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

Fix incorrect spelling of J9_PROJECT_SPECIFIC #5150

Merged
merged 1 commit into from
Apr 30, 2020

Conversation

aviansie-ben
Copy link
Contributor

It seems that previously, there was code in the Power codegen guarded by
the definition of a J9_ProjectSpecific macro. This was a misspelling of
the J9_PROJECT_SPECIFIC macro, so this code was never actually used.
This could cause incorrect behaviour in OpenJ9 if an irsload node
appeared under an s2i node. The spelling of this check has been
corrected so that the code should now be enabled correctly.

Fixed: #5137
Signed-off-by: Ben Thomas ben@benthomas.ca

It seems that previously, there was code in the Power codegen guarded by
the definition of a J9_ProjectSpecific macro. This was a misspelling of
the J9_PROJECT_SPECIFIC macro, so this code was never actually used.
This could cause incorrect behaviour in OpenJ9 if an irsload node
appeared under an s2i node. The spelling of this check has been
corrected so that the code should now be enabled correctly.

Fixed: eclipse-omr#5137
Signed-off-by: Ben Thomas <ben@benthomas.ca>
@fjeremic
Copy link
Contributor

@genie-omr build plinux,aix

@fjeremic
Copy link
Contributor

Not waiting for Travis since this is a Power only change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Investigate mis-spelled J9_ProjectSpecific code
2 participants