[GR-69548] Introduce -H:+PrintTypeStateMemoryFootprint #12143
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 PR introduces the
-H:+PrintTypeStateMemoryFootprint
option to print the estimated memory footprint forTypeState
instances. It shows how much memory is allocated forTypeStates
during analysis. This information can be used to compare analysis optimizations andTypeState
representation changes. I have a PR in progres that introduces a more compactMultiTypeState
and this PR provides a micrometric to measure its effects.The memory footprint report introduced in this PR is also generated automatically as a part of
-H:+PrintPointsToStatistics
. The new flag-H:+PrintTypeStateMemoryFootprint
is introduced because running the full-H:+PrintPointsToStatistics
is resource-intensive, so we want to allow computing just the footprint if the rest is not required.