hotspot JIT producing incorrect code -how should I report a bug?

[Chuck Rasbold]

Mark -

I don't think that you need to backport #6726504 and #6730192. The first
was just a clean up and the second a bug fix for the cleanup (he writes 
while eating humble pie).

As for the test case, I love it, but based on the channel in which the 
test case was submitted, Sun does not have ownership rights to the code, 
so I can't add it to OpenJDK. I am not a lawyer, but someone who is 
should feel free to correct me.

-- Chuck

On 09/25/08 14:57, Mark Wielaard wrote:
> Hi,
> 
> On Wed, Jul 16, 2008 at 02:23:21PM -0700, Chuck Rasbold wrote:
>> Ismael Juma wrote:
>>> Chuck Rasbold <Chuck.Rasbold at ...> writes:
>>>
>>>> Thanks for bringing 6707044 to our attention. Is was previously misfiled
>>>> in the wrong subcategory. I'm looking into a diagnosis right now.
>>> Thanks for looking into it Chuck. It looks like a scary bug and it would
>>> be very nice to get a fix.
>> With a fix now in jdk7/hotspot-comp/hotspot, we're now looking into
>> getting this fix backported into the 6u10 release.
> 
> This was indeed a scary bug. And easily triggered.
> I backported it to the jdk6 hotspot as used in icedtea.
> I also added the  test case for it (that obviously fails before and
> succeeds after the patch). It would be nice if it could also be added
> to the hotspot tests. There are unfortunately very little public tests
> for hotspot and increasing their number would help with making sure
> no regressings slip in.
> 
> I didn't take your followup patches (for #6726504 and #6730192) because
> I wanted a minimal backport. But if you think it would be good to
> backport those too then I will be happy to take a stab at it.
> 
> Cheers,
> 
> Mark
> 
> P.S. Note to Gary, I didn't try to fix it in the zero hotspot 7b24
>      version. We should probably just refresh that one completely.
>