-
Bug
-
Resolution: Fixed
-
P1
-
hs24, hs25
-
b34
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8018024 | 7u45 | Bengt Rutisson | P1 | Closed | Fixed | b01 |
| JDK-8009483 | 7u40 | Bengt Rutisson | P1 | Closed | Fixed | b34 |
There is no need to use atomics in create_new_gc_id() since it is not called by multiple threads in parallel. Also, Atomic::add(jlong, jlong *) can not be used unconditionally as it is not implemented on all 32-bit platforms.
We should remove the use of Atomic::add in create_new_gc_id() for now. If we need this to be called by multiple threads in the future we have to reconsider how this should be done. Either adding a lock or doing some kind of 32 bit atomic work.
Making this bug a P1 since JDK-8008314 is a P1.
We should remove the use of Atomic::add in create_new_gc_id() for now. If we need this to be called by multiple threads in the future we have to reconsider how this should be done. Either adding a lock or doing some kind of 32 bit atomic work.
Making this bug a P1 since JDK-8008314 is a P1.
- backported by
-
JDK-8009483 Remove redundant use of Atomic::add(jlong, jlong *) in create_new_gc_id()
-
- Closed
-
-
-
- Closed
-