[PING] Re: About time for b21?

[Joe Darcy]

Dr Andrew John Hughes wrote:
> On 16:19 Mon 27 Dec     , Joe Darcy wrote:
>   
>> Hello.
>>
>> Sorry for the tardy responses on OpenJDK 6 matters of late; I've been 
>> caught up working on a flurry of Project Coin activities.
>>
>>     
>
> Guessed it was something like that :-)
>
> Any idea when 7 will move into testing mode and 8 will become the main
> development arm?  I recall something about February?
>
>   
>> On 12/3/2010 5:59 AM, Dr Andrew John Hughes wrote:
>>     
>>> On 13:31 Tue 23 Nov     , Dr Andrew John Hughes wrote:
>>>       
>>>>>>> Building HS19 with Zero on PowerPC requires a fix (6994130).
>>>>>>> There's a webrev (for JDK7, but it's the same) here:
>>>>>>>
>>>>>>>   http://cr.openjdk.java.net/~gbenson/zero-ppc-fix/
>>>>>>>
>>>>>>> Would it be possible to backport this?
>>>>>>>               
>>>>>> Once 6994130 is approved and integrated into JDK 7, I approve it
>>>>>> being backported to OpenJDK 6.
>>>>>>             
>>>> It's now in b119 so presumably it can be backported?  Without it, the PPC build is broken
>>>> which is a regression from b20.
>>>>         
>> Yes, 6994130 has been in JDK 7 for a few builds so it can be backported 
>> to OpenJDK 6.
>>
>>     
>
> Done: http://hg.openjdk.java.net/jdk6/jdk6/hotspot/rev/fbc0d1be89ed
>
>   
>>>> We're still waiting on:
>>>>
>>>> http://mail.openjdk.java.net/pipermail/jdk6-dev/2010-October/002080.html
>>>>         
>>> 6668231: Presence of a critical subjectAltName causes JSSE's SunX509 to fail trusted checks
>>> Summary: make the critical extension known to end entity checker.
>>> Reviewed-by: wetmore, mullan
>>>
>>> Ok for push?  The binary keystores are copied as-is from OpenJDK7.
>>>
>>>       
>> The changes in 6668231 are approved for backporting.
>>
>>     
>
> Done: http://hg.openjdk.java.net/jdk6/jdk6/jdk/rev/acda21e83215
>
>   
>>>> http://mail.openjdk.java.net/pipermail/jdk6-dev/2010-September/002008.html
>>>>         
>> For the javac changes, backporting 6638712 in and of itself would be 
>> fine; however, backporting 6650759 would be problematic since it 
>> implements a type-inference specification change in JDK 7.  There are 
>> differences between the type inference behavior of javac in OpenJDK 6 
>> and the propriety JDK this issue is one of them.  The inference 
>> algorithm in OpenJDK 6 could be reworked a bit, but I don't expect the 
>> javac team to have cycles for that task in the near future.
>>
>>     
>
> Ok, we already have both fixes in IcedTea6.  They are necessary to be able
> to build JBoss AIUI.
>
>   
>>>> I'd also like to get:
>>>>
>>>> changeset:   2527:f1bafc4f249d
>>>> user:        peterz
>>>> date:        Tue Jun 29 14:42:30 2010 +0400
>>>> summary:     6963870: NPE in CompoundBorder.getInsets()
>>>> http://hg.openjdk.java.net/jdk7/jdk7/jdk/rev/f1bafc4f249d
>>>>
>>>> in as mentioned in http://mail.openjdk.java.net/pipermail/jdk6-dev/2010-August/001954.html
>>>>         
>> 6963870 is approved for backporting.
>>
>>     
>
> Done: http://hg.openjdk.java.net/jdk6/jdk6/jdk/rev/bc63cfb452f7
>
>   
>>>> As no solution for the hs19 bug has been forthcoming, I suggest we disable compressed oops
>>>> as we have in IcedTea6: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2010-November/010877.html
>>>>
>>>>         
>>> The compressed oops issue has now been fixed:
>>>
>>> changeset:   1873:4da76e32c0be
>>> user:        never
>>> date:        Wed Dec 01 10:16:31 2010 -0800
>>> summary:     7002666: eclipse CDT projects crash with compressed oops
>>> http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/4da76e32c0be
>>>
>>> Is there any movement on any of these patches being approved for OpenJDK6?
>>>
>>>       
>> Hmmm.  Perhaps it is more prudent to disable compressed oops in OpenJDK 
>> 6 b21 and then enable them in a subsequent build after a sync with hs20.
>>
>>     
>
> We've already backported this to IcedTea6 1.9 and it solves the issue with
> no further problems so far over the last month.  I'll leave the decision for
> OpenJDK6 up to you, but we'll have compressed oops enabled in IcedTea6 unless
> something else comes up.
>
> Once we decide which fix to push (7002666 or a disable oops), can we finally get
> b21 out the door?
>
>   

Hello.

Since you haven't run into any issues with having 7002666 in IcedTea6 
1.9, I'm satisfied to have it this build of OpenJDK 6, which should 
bring b21 to a close!

-Joe