RFR 8155771: [JVMCI] expose JVM_ACC_IS_CLONEABLE_FAST
tom.rodriguez at oracle.com
Mon May 2 18:40:47 UTC 2016
> On May 2, 2016, at 9:50 AM, Christian Thalinger <christian.thalinger at oracle.com> wrote:
>> On Apr 29, 2016, at 1:36 PM, Tom Rodriguez <tom.rodriguez at oracle.com <mailto:tom.rodriguez at oracle.com>> wrote:
>>> On Apr 29, 2016, at 4:10 PM, Christian Thalinger <christian.thalinger at oracle.com <mailto:christian.thalinger at oracle.com>> wrote:
>>>> On Apr 29, 2016, at 12:04 PM, Tom Rodriguez <tom.rodriguez at oracle.com <mailto:tom.rodriguez at oracle.com>> wrote:
>>>> http://cr.openjdk.java.net/~never/8155771/webrev <http://cr.openjdk.java.net/~never/8155771/webrev>+ boolean isAllocationCloneable();
>>> That means “allocation-cloneable”, not “allocation is cloneable”, right? It could be interpreted both ways but the change is good.
>> I knew what I meant so I didn’t see alternative readings. Is there something better? canBeClonedWithAllocation :)
> :-) Actually, that’s not a bad name. Or isClonableWithAllocation.
isClonableWithAllocation is ok, though it seems like it should be isCloneableWithAllocation?
>>>> The new flag JVM_ACC_IS_CLONEABLE_FAST controls whether an object can be cloned by simply performing an allocation and copying the fields. Previously all Cloneable objects were assumed to be cloneable in this way. Add ResolvedJavaType.isAllocationCloneable to expose this notion. Tested with Graal.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-compiler-dev