[lworld] RFR: 8334484: [lworld] new translation strategy for instance field initializers

[Maurizio Cimadamore]

On Fri, 28 Mar 2025 18:14:39 GMT, Maurizio Cimadamore <mcimadamore at openjdk.org> wrote:

>> Proxy locals are added as a new compiler phase which is executed just before code generation.
>> 
>> Q - what it does?
>> A - basically for code like:
>> 
>> abstract value class Super {
>>     Super(String s) {}
>> }
>> 
>> value class V extends Super {
>>     int i;
>>     V(String s) {
>>         if (s != null) {
>>             i = 100;
>>         } else {
>>             i = 200;
>>         }
>>         super("100" + s);
>>     }
>> }
>> 
>> javac will generate for V's constructor something in the lines of:
>> 
>>     V(String s) {
>>         /*synthetic*/ int local$i;
>>         if (s != null) {
>>             local$i = 100;
>>         } else {
>>             local$i = 200;
>>         }
>>         {
>>             /*synthetic*/ final String local$0 = "100" + s;
>>             i = local$i;
>>             super(local$0);
>>         }
>>     }
>> 
>> so given a constructor for which any strict field is assigned to more than once, javac will generate synthetic local variables that will correspond to it and any read or write done to this strict field will be done on the synthetic local variable.
>> 
>> Javac will also generate additional synthetic local variables to hold the arguments, if any, of the super constructor invocation and will assign the strict fields with the current value of the corresponding synthetic local just before invoking the super constructor.
>> 
>> Q - does it interacts with other valhalla features?
>> A - yes it has a direct interaction with the new stackmap table as the new assert_unset_fields entry, in most cases, is not generated now
>> Q- is it on by default?
>> A- yes but there is a hidden option to tell javac not to generate local proxy variables: `noLocalProxyVars` this will allow us to continue using javac for test cases that check for the generation of the assert_unset_fields entry in the stackmap table attribute until we have time to migrate those tests
>> 
>> TIA for any comments
>
> src/jdk.compiler/share/classes/com/sun/tools/javac/comp/LocalProxyVarsGen.java line 147:
> 
>> 145:                     if (t.hasTag(JCTree.Tag.METHODDEF)) {
>> 146:                         JCMethodDecl md = (JCMethodDecl) t;
>> 147:                         // ignore telescopic and generated constructors
> 
> I think TreeInfo::hasAnyConstructorCall might check this for you?

Uhmmm probably that doesn't deal with GENERATEDCONSTR (although -- a default constructor should not do much damage -- just maybe some redundant analysis?)

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

PR Review Comment: https://git.openjdk.org/valhalla/pull/1403#discussion_r2019139542