RFR(S): 8207773: [lworld] C2 should not allocate when returning a value type as Object from an inlined method (original) (raw)
Tobias Hartmann tobias.hartmann at oracle.com
Fri Jul 20 09:22:37 UTC 2018
- Previous message (by thread): RFR(S): 8207773: [lworld] C2 should not allocate when returning a value type as Object from an inlined method
- Next message (by thread): hg: valhalla/valhalla: 8207346: [lworld] C2 fails with "already heap allocated value types should be linked directly"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi John,
On 19.07.2018 09:11, John Rose wrote:
In the context of JDK-8207811 I'd suggest adding a comment saying something like "interfaces are handled above". The theory I'm proposing is that a bare test for Object (without interfaces also) needs an excuse. …But it's mainly a suggestion for avoiding future bugs, of a kind I've seen several times in the (long-gone) past.
Yes, I agree. I've added a link to this discussion to JDK-8207811 and will take care of it post-LW1.
OK. The name reads oddly; Object itself isn't (and so can't) be a value type, but can be a super of value types, and its domain is able to contain value instances; same point for any interface. I won't bikeshed here.
Yes, I'll change the naming with JDK-8207811.
Thanks, Tobias
- Previous message (by thread): RFR(S): 8207773: [lworld] C2 should not allocate when returning a value type as Object from an inlined method
- Next message (by thread): hg: valhalla/valhalla: 8207346: [lworld] C2 fails with "already heap allocated value types should be linked directly"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]