Good.
Thanks,
Vladimir
On 6/14/18 9:35 AM, Doug Simon wrote:
On 14 Jun 2018, at 12:03, Alan Bateman wrote:
On 14/06/2018 09:09, Doug Simon wrote:
In the context of JDK-8202762, we to need to make the jdk.aot module
upgradeable. Otherwise, it is impossible to run or test the version of
Doug,
Can you point (link) particular code which needs to be reviewed? And
what security issues could be?
Thanks,
Vladimir
On 4/19/17 2:12 PM, Doug Simon wrote:
3. Services.initializeJVMCI()
3 is harmless from a security perspective in my opinion.
Would be good if one of Oracle’s
Hotspot changes looks good to me.
Thanks,
Vladimir
On 4/19/17 2:26 PM, Doug Simon wrote:
I've updated http://cr.openjdk.java.net/~dnsimon/8177845/hotspot/ with these
changes:
1. JVMCIServiceLocator.getProvider(Class) is now protected
2. JVMCIServiceLocator.getProviders(Class) now checks
ReflectionAccessJDK ? Based on your comment in the file.
Vladimir
On 4/19/17 1:02 PM, Doug Simon wrote:
Sure - how about good old Util? ;-) I'm open to other suggestions.
Sent from my iPhone
On Apr 19, 2017, at 9:46 PM, Vladimir Kozlov <vladimir.koz...@oracle.com> wrote:
Hi Doug,
C
Hi Doug,
Can you consider using other name and not JDK9 for new JVMCI class? It
will be used in JDK 10 too:
jdk.vm.ci.services.internal.JDK9;
Thanks,
Vladimir
On 4/18/17 3:13 PM, Doug Simon wrote:
Please review these changes that make jdk.internal.vm.compiler an upgradable
compiler.
The
AOT tool jaotc does not run with SecurityManager. We assume it runs in secure
environment and it does not access any external resources.
Thanks
Vladimir
> On Feb 1, 2017, at 12:03 PM, Doug Simon wrote:
>
>
>> On 1 Feb 2017, at 20:54, Sean Mullan