RFR: 8267579: Thread::cooked_allocated_bytes() hits assert(left >= right) failed: avoid underflow [v2]

Stefan Karlsson stefank at openjdk.java.net
Wed Jun 9 13:54:14 UTC 2021


On Wed, 9 Jun 2021 13:36:31 GMT, David Holmes <dholmes at openjdk.org> wrote:

>> Markus Grönlund has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   read once
>
> src/hotspot/share/gc/shared/threadLocalAllocBuffer.cpp line 478:
> 
>> 476: }
>> 477: 
>> 478: const HeapWord* ThreadLocalAllocBuffer::start_relaxed() const {
> 
> Why do we need the "relaxed" terminology? By default accessors have no memory ordering properties.

I'm not sure what you are asking, but Atomic::load implements the "relaxed" semantics equivalent to using MO_RELAXED in the Access API.

-------------

PR: https://git.openjdk.java.net/jdk/pull/4363


More information about the hotspot-jfr-dev mailing list