RFR: 8257847: Tiered should publish MDO data pointer for interpreter after profile start [v3]
Dean Long
dlong at openjdk.java.net
Tue Dec 8 23:56:35 UTC 2020
On Tue, 8 Dec 2020 18:06:27 GMT, Igor Veresov <iveresov at openjdk.org> wrote:
>> Tiered policy may decide to start profiling in interpreter if C1 is overloaded with requests. It should publish an appropriate data pointer for the current bci in order for the interpreter to start profiling immediately and not wait for the second invocation.
>
> Igor Veresov has updated the pull request incrementally with one additional commit since the last revision:
>
> Make the code more robust
Marked as reviewed by dlong (Reviewer).
src/hotspot/share/compiler/tieredThresholdPolicy.cpp line 833:
> 831: if (mdo != NULL) {
> 832: JavaThread* jt = THREAD->as_Java_thread();
> 833: frame last_frame = jt->last_frame();
Some interpreter code is using LastFrameAccessor instead. Does it matter here?
-------------
PR: https://git.openjdk.java.net/jdk/pull/1683
More information about the hotspot-compiler-dev
mailing list