[GR-43979] Reachability trace prototype. #5883
Closed
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
oracle-contributor-agreement
bot
added
the
OCA Verified
graalvmbot
force-pushed
the
cs/GR-43979-print-reachability-trace
branch
from
4d3e870
to
b853170
Compare
graalvmbot
force-pushed
the
cs/GR-43979-print-reachability-trace
branch
3 times, most recently
from
da201b2
to
9c44431
Compare
graalvmbot
force-pushed
the
cs/GR-43979-print-reachability-trace
branch
2 times, most recently
from
73f8d87
to
82f4502
Compare
graalvmbot
force-pushed
the
cs/GR-43979-print-reachability-trace
branch
from
f840176
to
8d087ad
Compare
…tFieldReachabilityTrace
graalvmbot
force-pushed
the
cs/GR-43979-print-reachability-trace
branch
from
4f7130d
to
78247c8
Compare
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.
This PR explores adding some reachability tracing to the analysis. We aim to answer questions like: why is type
Xmarked as allocated, why is fieldY.fmarked as written, why is methodZ.foo()marked as invoked, etc. This kind of info is essential to reason about what the analysis proves as being run-time reachable.A good starting point is running the unit test in the PR:
mx build && mx native-unittest --build-args --features=com.oracle.svm.test.ReachableTypesFeature -- ReachabilityTraceTestingraal/substratevmand exploring what it does. It builds ahello-worldapp and it uses aFeatureto tap into theAnalysisUniverseand query various analysis elements. It currently prints to the console some reachability reasons for someAnalysisTypes, but it is just a prototype. We want to expand this tracing to cover various scenarios for all analysis elements (AnalysisField.written,AnalysisField.read,AnalysisMethod.inlined,AnalysisType.inHeap, etc.) and integrate it in our error messages eventually.