JDK-4679390 : sun.misc.Unsafe needs to bind to new JVM native methods
  • Type: Bug
  • Component: other-libs
  • Sub-Component: other
  • Affected Version: 1.4.1
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-05-03
  • Updated: 2002-05-14
  • Resolved: 2002-05-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.1 betaFixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
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.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: hopper-beta FIXED IN: hopper-beta INTEGRATED IN: hopper-beta
14-06-2004

EVALUATION Actions required: - wait for promotion of changes to unsafe.cpp in JVM - check in new version of Unsafe.java, based on sample in JVM sources ###@###.### 2002-05-03
03-05-2002