[jdk9] Forward-porting patches from 8u to 9
Alex Kashchenko
akashche at redhat.com
Thu Jun 23 20:41:50 UTC 2016
Hi,
On 06/15/2016 12:41 PM, Edward Nevill wrote:
> On Tue, 2016-06-14 at 17:59 +0100, Alex Kashchenko wrote:
>> Hi,
>>
>> I applied 8 patches from jdk8u to jdk9:
>>
>> - webrev:
>> http://cr.openjdk.java.net/~akasko/aarch32/jdk9/8155618_plus_7_other/webrev.00/
>>
>> Webrev is committed, all patches are the same as in 8u (with some
>> whitespace changes), all commit messages kept intact. They are tested
>> bootstrapping release version of jdk9 with a fastdebug one on multiple
>> devboards.
>
> Looks good. I am just doing some tests on it, and if all is OK will push
> it presently.
>
>> The following one is not included:
>>
>> - 8156067: aarch32: backport better byte behaviour
>> -
>> http://mail.openjdk.java.net/pipermail/aarch32-port-dev/2016-May/000265.html
>> - http://hg.openjdk.java.net/aarch32-port/jdk8u/hotspot/rev/e06cbcf76984
>>
>> PS: If there won't be objections I'll go on with updating jdk9 from
>> upstream and applying "better byte behaviour" patch.
>>
>
> No, no objections,
I looked into the aarch32-jdk9 forest updates. The current goal is to
update aarch32-jdk9 from jdk9/jdk9 merging at least up to jdk-9+116 tag
[1] to be able to apply and test aarch32 changes for "better byte
behaviour" issue.
The first step is to merge aarch32-jdk9 with jdk-9+99 [2]. This tag
contains two non-trivial hotspot changes:
- JDK-8132510: Replace ThreadLocalStorage with compiler/language-based
thread-local variables [3]
- JDK-8144534: Refactor templateInterpreter and
templateInterpreterGenerator functions [4]
aarch32 changes for these issues were applied on top of merged jdk-9+99
tag. Merge is clean for jdk repo, root repo has a minor conflict in a
non-functional part of generated_configure.sh, hotspot has a conflict in
threadLocalStorage.hpp that can be resolved the following way (accepting
mainline changes):
hg resolve -t internal:other
src/share/vm/runtime/threadLocalStorage.hpp
Other repositories in aarch32-jdk9 don't require merging - only need to
be updated to jdk-9+99 tag.
I'll post corresponding aarch32 changes in separate emails.
Build with these changes is checked to be functional ("java -version"
works), its testing (self-rebuild) is in progress.
[1] http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-April/004130.html
[2]
http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-December/003335.html
[3] https://bugs.openjdk.java.net/browse/JDK-8132510
[4] https://bugs.openjdk.java.net/browse/JDK-8144534
--
-Alex
More information about the aarch32-port-dev
mailing list