[lworld] RFR: 8311219: [lworld] VM option "InlineFieldMaxFlatSize" cannot work well [v2]

[Christian Lombardo]

Hello Team.
May you please unsubscribe me from this list, I'm changing careers :-) Keep up the great work everyone!

Love, Peace, Joy, Health, Wealth, Abundance, Happiness, Strength, Vitality, Power
Christian

Christian Lombardo, ME, OCPJP 1.6
christianlombardo at verizon.net
http://www.linkedin.com/in/christianlombardo
http://fortitudevolution.com/blog/ 

    On Thursday, August 17, 2023 at 01:19:31 AM EDT, Jatin Bhateja <jbhateja at openjdk.org> wrote:  
 
 On Thu, 17 Aug 2023 01:51:08 GMT, Xiaohong Gong <xgong at openjdk.org> wrote:

> > Just going slightly off the topic, in context of Vector APIs (lworld+vector) all the payloads are final primitive class fields and will always be flattened in their respective boxes.
> 
> Sorry for my late reply! And yes, the payloads in Vector APIs are always be flattened for current vector size. What my concern is the larger vector size like in Arm SVE after we support the SPECIES_MAX vectors, and the expected behavior/difference if people set a smaller max flat size with `InlineFieldMaxFlatSize`.
> 
> Thanks, Xiaohong

That's correct!, my above comment was in context of existing handling where final fields of [null-restricted value types](https://openjdk.org/jeps/401) are always flattened irrespective of InlineFieldMaxFlatSize.  Are you inclined to re-instantiate the old behavior ?

Best Regards,
Jatin

-------------

PR Comment: https://git.openjdk.org/valhalla/pull/888#issuecomment-1681627002
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/valhalla-dev/attachments/20230819/8c39c095/attachment.htm>