Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 24
Affects Version/s: None
Component/s: hotspot
Labels:
- sync

Subcomponent:
runtime
Resolved In Build:
b18

The ObjectMonitor successor protocol designates a Responsible thread to avoid a memory barrier when storing null in the owner for unlocking a monitor. The cost of memory barriers is a lot lower than 20+ yrs ago when this was implemented. We could simplify this code by adding the write barrier and removing Responsible.

Performance test this, of course.

relates to

JDK-8339730 Windows regression after removing ObjectMonitor Responsible

Resolved

JDK-8341333 [JVMCI] Export JavaThread::_unlocked_inflated_monitor to JVMCI

Resolved

JDK-8342830 Regression ~24% in DaCapo23-spring-large after JDK-8320318 only Windows

Closed

JDK-8276851 [AArch64] Improve fast_unlock C2 intrinsic

Closed

JDK-8341854 Incorrect clearing of ZF in fast_unlock_lightweight on x86

Resolved

JDK-8342042 PPC64: compiler_fast_unlock_object flags failure instead of success

Resolved

JDK-8342683 Use non-short forward jump when passing stop()

Resolved

links to

Commit(master) openjdk/jdk/180affc5

Review(master) openjdk/jdk/19454

(2 relates to, 2 links to)

Assignee:: Fredrik Bredberg

Reporter:: Coleen Phillimore

Votes:: 0 Vote for this issue

Watchers:: 14 Start watching this issue

Created:: 2023-11-17 06:17

Updated:: 2024-10-22 06:38

Resolved:: 2024-09-30 05:29

Details

Description

Attachments

Issue Links

Activity

People

Dates