RFR: 8343685: C2 SuperWord: refactor VPointer with MemPointer [v6]
    Christian Hagedorn 
    chagedorn at openjdk.org
       
    Wed Jan 15 13:08:57 UTC 2025
    
    
  
On Wed, 15 Jan 2025 12:13:59 GMT, Christian Hagedorn <chagedorn at openjdk.org> wrote:
>> Emanuel Peter has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   More fixes for vnkozlov
>
> src/hotspot/share/opto/vectorization.hpp line 844:
> 
>> 842:   }
>> 843: 
>> 844:   bool has_same_invar_and_iv_scale_as(const VPointer& other) const {
> 
> Okay, I see that we should probably use either "invariant" or "invar" consistently in method names. I guess it's still fine for temporary variables to use "invar". But when reading code it could be more clear when using "invariant". But I leave it up to you to decide - having a better big picture if this is improving the readability or not.
Should we name this ...same_invar_summands... to be more precise?
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/21926#discussion_r1916515961
    
    
More information about the hotspot-compiler-dev
mailing list