Change DLT opt level based on option #20857
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mpirvu
added
the
depends:omr
Before this change one could force the optimization
level of a particular DLT compilation through a
command line option (dltOptLevel=...) only if the
TR_DebugDLT env var was defined. This was done to avoid
the overhead of searching the option subsets for a
given method.
This commit allows one to specify the optimization level
of DLT compilations without the need of an env var.
Examples:
-Xjit:dltOptLevel=hot
-Xjit:{myMethod}(dltOptLevel=cold)
The overhead for searching option sets has been eliminated
if no option subset uses the dltOptlevel= option
Depends on eclipse-omr/omr#7596
Signed-off-by: Marius Pirvu <[email protected]>
|
Jenkins test sanity xlinux jdk21 depends eclipse/omr#master |
|
The omr dependency has reached the openj9-omr repo, so this PR can be reviewed/merged. |
|
it has been tested. merging ... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Before this change one could force the optimization level of a particular DLT compilation through a command line option (dltOptLevel=...) only if the TR_DebugDLT env var was defined. This was done to avoid the overhead of searching the option subsets for a given method.
This commit allows one to specify the optimization level of DLT compilations without the need of an env var. Examples:
-Xjit:dltOptLevel=hot
-Xjit:{myMethod}(dltOptLevel=cold)
The overhead for searching option sets has been eliminated if no option subset uses the dltOptlevel= option
Depends on eclipse-omr/omr#7596