Re: Experimental patches for unsafe cleanup Re: The s.m.Unsafe representation in hotspot and method registration

2014-03-25 Thread Paul Sandoz
On Mar 25, 2014, at 2:37 PM, Staffan Larsen wrote: > (Adding hotspot-runtime-dev since some changes are in hotspot code). > > > On 25 mar 2014, at 14:20, Paul Sandoz wrote: > >> >> On Mar 25, 2014, at 9:34 AM, Paul Sandoz wrote: >> >>> >>> On Mar 24, 2014, at 7:49 PM, Staffan Larsen >>

Re: Experimental patches for unsafe cleanup Re: The s.m.Unsafe representation in hotspot and method registration

2014-03-25 Thread Staffan Larsen
(Adding hotspot-runtime-dev since some changes are in hotspot code). On 25 mar 2014, at 14:20, Paul Sandoz wrote: > > On Mar 25, 2014, at 9:34 AM, Paul Sandoz wrote: > >> >> On Mar 24, 2014, at 7:49 PM, Staffan Larsen >> wrote: >> >>> We have abandoned the HSX model. From JDK 8 one versi

Experimental patches for unsafe cleanup Re: The s.m.Unsafe representation in hotspot and method registration

2014-03-25 Thread Paul Sandoz
On Mar 25, 2014, at 9:34 AM, Paul Sandoz wrote: > > On Mar 24, 2014, at 7:49 PM, Staffan Larsen wrote: > >> We have abandoned the HSX model. From JDK 8 one version of Hotspot will be >> tied to one version of the JDK. This looks like old code that has not been >> cleaned up. >> > > Thanks

Re: The s.m.Unsafe representation in hotspot and method registration

2014-03-25 Thread Paul Sandoz
On Mar 24, 2014, at 7:49 PM, Staffan Larsen wrote: > We have abandoned the HSX model. From JDK 8 one version of Hotspot will be > tied to one version of the JDK. This looks like old code that has not been > cleaned up. > Thanks, yes, looks like we can clean this up and also remove the deprec

Re: The s.m.Unsafe representation in hotspot and method registration

2014-03-24 Thread Staffan Larsen
We have abandoned the HSX model. From JDK 8 one version of Hotspot will be tied to one version of the JDK. This looks like old code that has not been cleaned up. /Staffan On 24 mar 2014, at 19:13, Peter Levart wrote: > > On 03/24/2014 07:02 PM, Paul Sandoz wrote: >> On Mar 24, 2014, at 6:37

Re: The s.m.Unsafe representation in hotspot and method registration

2014-03-24 Thread Paul Sandoz
On Mar 24, 2014, at 6:37 PM, Joel Borggrén-Franck wrote: > Hi Paul, > > I would guess this is because of the HSX model where we could use the same VM > with different majors of the JDK. Would that make sense? > I was wondering about too, but does that still apply to JDKs 1.4.0, 1.4.1, 1.5

Re: The s.m.Unsafe representation in hotspot and method registration

2014-03-24 Thread Peter Levart
On 03/24/2014 07:02 PM, Paul Sandoz wrote: On Mar 24, 2014, at 6:37 PM, Joel Borggrén-Franck wrote: Hi Paul, I would guess this is because of the HSX model where we could use the same VM with different majors of the JDK. Would that make sense? I was wondering about too, but does that sti

Re: The s.m.Unsafe representation in hotspot and method registration

2014-03-24 Thread Joel Borggrén-Franck
Hi Paul, I would guess this is because of the HSX model where we could use the same VM with different majors of the JDK. Would that make sense? cheers /Joel On 24 Mar 2014, at 17:42, Paul Sandoz wrote: > I started working on a patch to remove the monitor related methods on Unsafe, > and was