[9] RFR (S): 8140001: _allocateInstance intrinsic does not throw InstantiationException for abstract classes and interfaces

Aleksey Shipilev aleksey.shipilev at oracle.com
Thu Jan 14 15:15:52 UTC 2016

Looks okay to me, but I think the property name should reflect Java
terminology, e.g. "can_be_instantiated", "not is_allocatable"?

$ javac AbstractSample.java
[ERROR] AbstractSample.java:[36,9] AbstractSample.M is abstract; cannot
be instantiated


On 01/14/2016 06:05 PM, Vladimir Ivanov wrote:
> Any feedback, please?
> Best regards,
> Vladimir Ivanov
> On 1/12/16 6:22 PM, Vladimir Ivanov wrote:
>> http://cr.openjdk.java.net/~vlivanov/8140001/webrev.00/
>> https://bugs.openjdk.java.net/browse/JDK-8140001
>> EA can eliminate allocations of abstract classes or interfaces, thus
>> changing observable behavior of a program as the test case demonstrates.
>> The fix is to always mark such allocations as escaping.
>> Testing: failing test, JPRT.
>> Thanks!
>> Best regards,
>> Vladimir Ivanov

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20160114/bb4630f5/signature.asc>

More information about the hotspot-compiler-dev mailing list