jilconst: don't redefine OMR_GC_CONCURRENT_SCAVENGER #15455
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a corrected version of #15406: When defined, continue to write
OMR_GC_CONCURRENT_SCAVENGER
tojilvalues
.For platforms that include
j9cfg.h
, avoid generating a duplicate, conflicting definition injilconsts
.Add missing include in
aarch64/runtime/Recompilation.spp
.