RFR: Some build fixes for gcc4.7

[Roman Kennke]

Am Montag, den 07.01.2013, 14:40 -0800 schrieb Christian Thalinger:
> On Jan 7, 2013, at 12:59 PM, Roman Kennke <rkennke at redhat.com> wrote:
> 
> > Am Donnerstag, den 13.12.2012, 12:41 -0800 schrieb Christian Thalinger:
> >> On Dec 12, 2012, at 12:19 AM, Roman Kennke <rkennke at redhat.com> wrote:
> >> 
> >>> Hi David,
> >>> 
> >>>> From my perspective, there are the following proposed changes not
> >>> committed yet:
> >>> 
> >>> 1.
> >>> http://mail.openjdk.java.net/pipermail/hotspot-dev/2012-November/007294.html
> >>> 
> >>>> From that one, only the jdk part is missing:
> >>> http://cr.openjdk.java.net/~rkennke/shark/webrev-jdk-00/
> >>> 
> >>> I think it's the only one with a bug-id even:
> >>> 8003868: fix shark for latest HotSpot and LLVM
> >>> 
> >>> 2. Then there is the library_call build fixes. (Which have also been
> >>> proposed by Yasumasa Suenaga, which now got the bug id 8004898 and
> >>> Christian is working on it.)
> >>> 
> >>> Then I posted a bunch of others on hotspot-compiler-dev (maybe
> >>> hotspot-dev would have been better?)
> >>> 
> >>> 3. Fix OSR in Shark for non-empty incoming stack
> >>> http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2012-December/009087.html
> >>> 
> >>> This one got a little review by David Chase, for which I will send an
> >>> updated webrev soon. I was hoping to get some more feedback though, or
> >>> even a bug-id.
> >>> 
> >>> 4. Implement deoptimization support in Shark
> >>> http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2012-December/009088.html
> >>> 
> >>> This one did not get any feedback yet, no bug-id either.
> >>> 
> >>> 5. Fix volatile float field access in Shark 
> >>> http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2012-December/009089.html
> >>> 
> >>> Same, no feedback, no bug-id.
> >>> 
> >>> 6. Enable JSR292 support in Shark
> >>> http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2012-December/009090.html
> >>> 
> >>> Got some positive feedback from John Rose, but no bug id and no
> >>> progress.
> >>> 
> >>> Please let me know if I should do anything different in the future
> >>> (different mailing list, different format, ..) Also, if it helps, I can
> >>> group all those changes into one big change, I just thought that it is
> >>> easier to review in logical chunks (otherwise the changes would
> >>> interleave and it's difficult to say what belongs to what).
> >> 
> >> Currently we have some problems with JPRT so I waiting for that to be resolved.  But I will take care of all the above.
> > 
> > Hi,
> > 
> > Is there any progress on these issues? Maybe at least give it a Bug ID
> > so it's not forgotten?
> 
> Yes, and I'm sorry about that.  Let me create some bugs right now.

Thanks alot!

Cheers,
Roman