JDK-8024648 : 7141246 & 8016131 break Zero port
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7u40
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-09-11
  • Updated: 2014-10-15
  • Resolved: 2014-02-26
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.
JDK 7
7u60 b09Fixed
Related Reports
Relates :  
JDK-8016131 - nsk/sysdict/vm/stress/chain tests crash the VM in 'entry_frame_is_first()'
Relates :  
JDK-8022188 - Make zero compile after 8016131 and 8016697
Description
Reported by Andrew on jdk7u-dev mailing list :

===
It appears that Zero is broken in u40 by 8016131.  How do I go about getting
this fix [1] into the u40 branch?  Is that possible?

[0] http://mail.openjdk.java.net/pipermail/jdk7u-dev/2013-August/007592.html
[1] http://icedtea.classpath.org/hg/release/icedtea7-forest-2.4/hotspot/rev/09f439dfd7b9
===

http://mail.openjdk.java.net/pipermail/jdk7u-dev/2013-September/007680.html
Comments
SQE is ok to take the fix in 7u60.
25-02-2014
These are build issues, regression test is not applicable. I'll add noreg-build.
24-02-2014
The fix was pushed to 7u-dev, the change is available in the 7u80 backport http://hg.openjdk.java.net/hsx/jdk7u/hotspot/rev/ff18bcebe294 There does not seem to be a regression test. Andrew, does such a test exist, or is there a reason why no regression test could be made?
24-02-2014
Critical Request Motivation This is a regression introduced in 7u40, we should get this fixed as soon as possible.
21-02-2014
Open for many months now. I've asked Andrew if he can supply the patch. http://mail.openjdk.java.net/pipermail/jdk7u-dev/2014-January/008294.html
23-01-2014
Fair enough. Note that changes in a jdk8 repo are not automatically backported to 7u next (currently 7u60), someone has to initiate the backport (get the change exported/imported, reviewed, etc) Since it is in the hs-rt repo (hs25), bring it into a clone of the hotspot repo for jdk7u60 (see [1] for details), get it reviewed and once it has been cleared for pushing, I can get it pushed, via JPRT, into the hotspot repo (hsx/jdk7u/hotspot). [1] http://mail.openjdk.java.net/pipermail/hotspot-dev/2013-September/011015.html
24-09-2013
a) This bug was filed against u40, not u60. u60 will no doubt receive 8022188 in due course from the 8 repositories (http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/c54a3122f9c8). I wanted to fix the fact that Zero is broken in u40 but apparently OpenJDK doesn't maintain its releases, it just freezes them and lets them rot. b) I don't think legally you can just go plucking our code from the IcedTea repositories as the OpenJDK web pages say they need to be contributed under the OCA (http://openjdk.java.net/legal/)
24-09-2013
The hotspot forest (hsx/jdk7u) corresponding to jdk7u60 (jdk7u/jdk7u) are now in place, so I will export the changeset from the above icetea repo and will push it to hsx/jdk7u via jprt in the next few days. It will make it to jdk7u/jdk7u/hotspot when we push the first snapshot of hsx/jdk7u/hotspot to it, most likely next week.
19-09-2013