[GR-52732] Optimize stack trace information for implicit exceptions. #8675
Conversation
This file contains hidden or 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
oracle-contributor-agreement
bot
added
the
OCA Verified
graalvmbot
force-pushed
the
cwi/GR-52732-implicit-exceptions
branch
from
1d35087 to
7ca21b6
Compare
graalvmbot
force-pushed
the
cwi/GR-52732-implicit-exceptions
branch
from
7ca21b6 to
94d2796
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds a phase that reduces the runtime metadata for implicit exceptions, at the cost of stack trace precision. See the JavaDoc of
ReduceImplicitExceptionStackTraceInformationPhasefor details how it works.Because stack trace information is important for development and debugging, the phase is only enable by default for the
-O3optimization level. That also enables it for--pgobuilds.