Re: notes from Valhalla meeting 5/24/17

On Jun 21, 2017, at 4:44 PM, Paul Sandoz wrote: > > A BSM called to resolve a constant can choose when pulling it’s static args > to catch and swallow linkage exceptions, keep on trucking, and return a > value. Should this be allowed? Absolutely. The BSM might have an

Re: notes from Valhalla meeting 5/24/17

Thanks; all fixed. On Jun 21, 2017, at 1:45 PM, Paul Sandoz wrote: > > > "This allows the bootstrap logic the ability to order the resolution of > constants and catch linkage exceptions.” > > And possibly still link a constant rather than re-throwing a linkage >

Re: notes from Valhalla meeting 5/24/17

net>, > valhalla-spec-experts@openjdk.java.net > Envoyé: Mercredi 21 Juin 2017 18:03:49 > Objet: Re: notes from Valhalla meeting 5/24/17 > > [...] > It only repurposes the concept of field names and field types > (as if from Fieldref but not using Fieldref) but does not actuall

Re: notes from Valhalla meeting 5/24/17

> De: "John Rose" <john.r.r...@oracle.com> > À: "Rémi Forax" <fo...@univ-mlv.fr> > Cc: "Valhalla Expert Group Observers" > <valhalla-spec-observ...@openjdk.java.net>, > valhalla-spec-experts@openjdk.java.net > Envoyé: Mercredi 21 J

Re: notes from Valhalla meeting 5/24/17

On Jun 21, 2017, at 8:46 AM, Remi Forax wrote: > > but i do not like with this proposal as is, i will explain why and how to fix > it: > - condy is linked to a static final field but unlike invokedynamic which is a > link from an invokedynamic instruction to a

Re: notes from Valhalla meeting 5/24/17

edi 21 Juin 2017 10:46:22 > Objet: Re: notes from Valhalla meeting 5/24/17 > On Jun 19, 2017, at 6:28 PM, John Rose <john.r.r...@oracle.com> wrote: >> >> I have updated the javadoc portion of the spec for constant-dynamic. >> There are small but strategic changes to

Re: notes from Valhalla meeting 5/24/17

On Jun 19, 2017, at 6:28 PM, John Rose wrote: > > I have updated the javadoc portion of the spec for constant-dynamic. > There are small but strategic changes to MethodType and MethodHandle, > as well as new classes to represent the "pull mode" of constant resolution. >

Re: notes from Valhalla meeting 5/24/17

On Jun 9, 2017, at 1:51 PM, John Rose wrote: > > We have talked about "condy" (a constant-pool friend for indy). > Enclosed is the javadoc portion of a draft spec. > The JVM spec. is not ready and will be sent separately. > This javadoc reflects code checked into the

UFoo; ?? Was: notes from Valhalla meeting 5/24/17

from any to Bar when we need the value represented by '? extends Bar'. so why do we need UFoo; ?? Rémi > De: "Karen Kinnear" <karen.kinn...@oracle.com> > À: valhalla-spec-experts@openjdk.java.net > Envoyé: Mardi 6 Juin 2017 01:21:59 > Objet: notes from Valhalla me

notes from Valhalla meeting 5/24/17

Corrections welcome - I confess I had a fever while taking notes - so particularly at the end, my notes are less coherent. For the meeting Wednesday June 7, we need to discuss short-term MVT constant pool representation for value types - CONSTANT_Class_info with “;QFoo;” vs.