Can't run Graal with JDK 11
aph at redhat.com
Wed May 2 10:01:56 UTC 2018
On 05/02/2018 10:18 AM, Doug Simon wrote:
>> On 2 May 2018, at 11:08, Andrew Haley <aph at redhat.com> wrote:
>> On 05/02/2018 09:55 AM, Doug Simon wrote:
>>> Until that's done, I agree that getting work done on jaotc will be
>>> challenging. The only workaround I can think of is to use the `mx
>>> updategraalinopenjdk` command as part of your workflow.
>> That sounds like it would probably work, but of course it corrupts the
>> source of the OpenJDK I'm working on.
> The updategraalinopenjdk tool should only touch the Graal
> directories in OpenJDK. If not, it's a bug and will be fixed.
Sure, but it's tricky to think about how the process works. If I make
back-end changes then I sometimes have to make small tweaks to the
Graal sources inside OpendJDK so as not to break builds. So, I'll
have to keep two parallel build trees.
>> I guess I can live with that for now, but as Graal is part of
>> OpenJDK and seems likely to be important we're going to have to
>> make it easier for people to work on. In the long run, as you
>> might expect, I'd prefer it to be a first-class part of OpenJDK.
> Yes, I agree that would simplify the OpenJDK development
> process. However, Graal is used in a number of other contexts and as
> such needs to be developed and tested independently of OpenJDK. We
> will continue to try mitigate OpenJDK development pain by providing
> tools such as updategraalinopenjdk.
Fair enough. My primary concern is -- of course -- how to minimize
pain for myself, but also to encourage more contributors to OpenJDK.
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the hotspot-compiler-dev