RFR: 8290834: Improve potentially confusing documentation on collection of profiling information [v7]
Julian Waters
jwaters at openjdk.org
Sat Jul 23 13:59:59 UTC 2022
> Documentation on the MethodData object incorrectly states that it is used when profiling in tiers 0 and 1, when it only does so for tier 0 (Interpreter), while tier 1 (Fully optimizing C1) does not collect any profile data at all. Additionally, the description for the different execution tiers is slightly misleading, as it seems to imply that MethodData is used in tier 3 as well, when profiling with C1 is done through ciMethodData instead. This cleanup attempts to slightly better clarify how profiling is tied together between the Interpreter and C1, explain what MDO is an abbreviation for (MethodData object), and corrects the documentation for MethodData as well.
Julian Waters has updated the pull request incrementally with one additional commit since the last revision:
Fixup
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/9598/files
- new: https://git.openjdk.org/jdk/pull/9598/files/c48d67f3..a6b75011
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=9598&range=06
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=9598&range=05-06
Stats: 12 lines in 2 files changed: 1 ins; 1 del; 10 mod
Patch: https://git.openjdk.org/jdk/pull/9598.diff
Fetch: git fetch https://git.openjdk.org/jdk pull/9598/head:pull/9598
PR: https://git.openjdk.org/jdk/pull/9598
More information about the hotspot-compiler-dev
mailing list