Backport multiple toolchains support to JDK8?
martinrb at google.com
Tue May 12 17:43:20 UTC 2015
I also think that backporting multiple toolchain support seems too risky
for jdk8u. At the same time, it may be very useful for others trying to
test or port the jdk8u code base (at google, we are motivated by running
asan via clang). It would be good if there was a way to share such a
backport without being integrated into the jdk8u forest proper. Currently
the only way supported by openjdk infrastructure is a webrev, I think...
On Mon, May 11, 2015 at 5:19 AM, Magnus Ihse Bursie <
magnus.ihse.bursie at oracle.com> wrote:
> On 2015-05-08 18:49, Alexander Smundak wrote:
>> And I guess the successor of the 8u60 is going to be the last JDK8
> As far as I know, 8u60 is the last JDK8 feature release being done by
>> On Fri, May 8, 2015 at 2:00 AM, Magnus Ihse Bursie
>> <magnus.ihse.bursie at oracle.com> wrote:
>>> On 2015-05-08 04:46, Alexander Smundak wrote:
>>>> I have backported "8034788: Rewrite toolchain.m4 to support multiple
>>>> toolchains per platform." and related changes to jdk8u40 in order to
>>>> build JDK8 with Clang/LLVM on Linux. Can I mail this change for the
>>> JDK 8u40 is already released. Did you mean 8u60?
>>> To get a backport in 8u60 means you need to get approval according to
>>> If the backport does not apply cleanly (which I suspect in this case),
>>> you also need a review from the build team.
>>> As I understand, 8u60 is already feature complete, and this change in
>>> question is quite intrusive. I would not recommend backporting it to
>>> 8u60 at
>>> this point.
More information about the build-dev