On Tue, 27 Oct 2026 22:45:26 GMT, Mat Carter <[email protected]> wrote:
>> My initial reaction was that the field should just be declared as volatile, >> because the accesses that don't need this are not in places where there >> would be noticeable performance impact. I'm back to thinking this is the >> best fix.. > >> My initial reaction was that the field should just be declared as volatile, >> because the accesses that don't need this are not in places where there >> would be noticeable performance impact. I'm back to thinking this is the >> best fix.. > > @DougLea, Given that this PR fixes the issue; are you open to keeping this > simple change as is and creating another issue to optimize/simplify the > solution? @macarte I never have an opinion about process issues! Changing this one or creating another both seem fine. ------------- PR Comment: https://git.openjdk.org/jdk/pull/33551#issuecomment-6456402760
