> On 16 Feb 2017, at 19:30, Vladimir Kozlov wrote:
>
> Hi Doug,
>
> Is it because of next change?:
>
> module jdk.internal.vm.ci {
> - exports jdk.vm.ci.services;
> + exports jdk.vm.ci.services to jdk.internal.vm.compiler;
>
> But you said before that your version of graal has the
Hi Doug,
Is it because of next change?:
module jdk.internal.vm.ci {
- exports jdk.vm.ci.services;
+ exports jdk.vm.ci.services to jdk.internal.vm.compiler;
But you said before that your version of graal has the same module name. Why
you need --add-exports?
Thanks,
Vladimir
On 2/
Thank you, Magnus
Vladimir
On 2/15/17 11:54 PM, Magnus Ihse Bursie wrote:
On 2017-02-16 02:37, Vladimir Kozlov wrote:
https://bugs.openjdk.java.net/browse/JDK-8174879
jdk.vm.ci and jdk.vm.compiler are purely JVM internal modules that is only of
interest to VM developers (and
researchers), no
Just to note here, this means an external version of Graal will now have to use
--add-exports VM options to access JVMCI. Which is ok since additional VM
options are required anyway to put an external Graal on the module path.
-Doug
> On 16 Feb 2017, at 08:54, Magnus Ihse Bursie
> wrote:
>
>
On 2017-02-15 18:12, Claes Redestad wrote:
Hi,
currently the file we generate at build time as input to
--generate-jli-classes is lost when linking custom images, which means
user generate images may perform worse in certain ways, mostly
generating more classes during startup.
Additionally, the
