-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P1
-
Affects Version/s: 1.4.2
-
Component/s: hotspot
-
07
-
x86, sparc
-
solaris_8, windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2065986 | 5.0 | James Mcilree | P1 | Closed | Fixed | b03 |
| JDK-2065985 | 1.4.2 | James Mcilree | P1 | Closed | Fixed | b19 |
There are three problems with x86 membar:
1) It's a no-op on win32
2) Linux uses sfence, instead of mfence, doing only store barriers
3) Solaris x86 claims to do a mfence, but uses the sfence encoding!
This is a critical flaw. There is a reproducable VM crash on win32,
and the solx86/linux bug could easily result in random VM crashes.
1) It's a no-op on win32
2) Linux uses sfence, instead of mfence, doing only store barriers
3) Solaris x86 claims to do a mfence, but uses the sfence encoding!
This is a critical flaw. There is a reproducable VM crash on win32,
and the solx86/linux bug could easily result in random VM crashes.
- backported by
-
JDK-2065985 atomic::membar doesn't on x86
-
- Closed
-
-
-
- Closed
-
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-