8024648: 8016131 breaks Zero port was (Re: [7u communication] JDK 7u40 released today!)

[Seán Coffey]

Alejandro,

8022188 addresses a fix to Zero port necessary since 8016131 and 8016697 
integrations to hs25.
Since 8016697 isn't in hs24, it might be better have the new bug ID 
follow this issue [1]. I've assigned that to Andrew and he already has a 
changeset in icedtea [2].

I understand that there's a new hsx forest naming convention for hsx 
fixes targeting jdk7u [3]. Please ping the jdk7u-dev at openjdk.java.net 
mailing list when this new forest structure is in place.

regards,
Sean.

[1] http://bugs.sun.com/view_bug.do?bug_id=8024648
[2] 
http://icedtea.classpath.org/hg/release/icedtea7-forest-2.4/hotspot/rev/09f439dfd7b9
[3] 
http://mail.openjdk.java.net/pipermail/hotspot-dev/2013-August/010683.html

On 11/09/2013 23:02, Alejandro E Murillo wrote:
>>>>
>>>> 8024648: 8016131 breaks Zero port
>>> That was part of my point.  There's some mention of 7u40 appearing 
>>> in mid-September
>>> and then it suddenly appears yesterday evening, with no further 
>>> warning.  I was still
>>> testing builds of it on various platforms and would have liked to 
>>> have include the Zero
>>> fix in u40.
>> This issue should have been raised back in early August when 8022188 
>> was reported. Has anyone been testing Zero builds for 7u codebase? 
>> It's a team effort. 7u40 has been ramping down since mid June [1]
>>>
>>> I'm not sure there's much point putting it in u60 as no doubt 
>>> they'll be a further HotSpot pull
>>> which will pick up 8022188 [0] already mentioned by Omair.  I didn't 
>>> find that changeset
>>> until I'd already written the same fix (identical in fact) for u40 
>>> and Omair's couldn't be
>>> backported anyway as it carries other changes (a habit I, 
>>> incidentally, prefer to avoid).
>>> I'm happy to push my version though, if wanted.
>>>
>>> However, my main concern is that u40 won't built Zero.  Are there 
>>> going to be no further updates to it,
>>> not even for security fixes?
>> Let's get the fix into the 7u forest (via hsx). CPU changesets get 
>> pushed to the jdk7u forest when the CPU releases.
> I will bring this to the 7u forest in the next couple of days
> via the new hsx repo for 7u (hsx/jdk7u/hotspot, which will be created 
> soon).
>
> Just to double check, we basically need to backport this changeset:
> http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/c54a3122f9c8
>
> correct?