-
Bug
-
Resolution: Fixed
-
P3
-
1.4.1
-
beta
-
generic
-
generic
This is a follow-up to bug 4616656, which requires the VM to support
certain 64-bit unsafe operations, based on a request by Oracle.
4616656 3/1 Need a more portable way to unsafely access fields in JDk 1.4
In order to complete this work, a new backward compatible version of
Unsafe.java needs to be checked into the SDK. No other code changes are
required. See the sample version of Unsafe.java in the hotspot workspace,
subdirectory "doc", after the fix for 4616656 is promoted.
certain 64-bit unsafe operations, based on a request by Oracle.
4616656 3/1 Need a more portable way to unsafely access fields in JDk 1.4
In order to complete this work, a new backward compatible version of
Unsafe.java needs to be checked into the SDK. No other code changes are
required. See the sample version of Unsafe.java in the hotspot workspace,
subdirectory "doc", after the fix for 4616656 is promoted.
- relates to
-
JDK-4653558 Java Application startup time is SLOW in JDK 1.4 compared to JDK 1.3.1_02
-
- Closed
-
-
JDK-4693297 Performance regression in sun.misc.Unsafe 64-bit restructuring
-
- Closed
-
-
JDK-4684781 ObjectStreamClass should use long sun.misc.Unsafe field offsets
-
- Resolved
-
-
JDK-4690509 Sybase Java Application startup time is SLOW in JDK 1.4 compared to JDK 1.3.1_02
-
- Closed
-
-
JDK-4616656 Need a more portable way to unsafely access fields in JDk 1.4
-
- Closed
-