RFR: 8366490: C2 SuperWord: wrong result because CastP2X is missing ctrl and floats over SafePoint creating stale oops [v3]

[Christian Hagedorn]

On Tue, 2 Sep 2025 13:09:32 GMT, Emanuel Peter <epeter at openjdk.org> wrote:

>> **Analysis**
>> 
>> A `CastP2X` without ctrl can float. If it floats over a `SafePoint` (or call), we may GC and move the oop. But the `CastP2X` value does not end up on the oop-map, and so the pointer is stale (old).
>> 
>> With `StressGCM`, the aliasing runtime check has one `CastP2X` that floats over the SafePoint, and another that stays after the SafePoint. Both read the oop of the same array, so instead of getting the same address, we now get the old and the new oop. And so the aliasing runtime check passes (thinks there is no aliasing), even though there is aliasing. We end up vectorizing, which reorders the loads/stores and would only be safe if there is no aliasing.
>> 
>> **Fix:** add control to the `CastP2X` so that it cannot float too far.
>> 
>> **Details**
>> 
>> 
>> rbp = Allcoate array
>> spill <- rbp + 0x20
>> 
>> call to allocateArrays
>> -> allocates a lot, and triggers GC. That moves the allocated array behind rbp
>> -> rbp is oop-mapped, so it is updated automatically to the new oop
>> -> spill value remains based on the old oop
>> 
>> We now compute the aliasing runtime check:
>> -> one side of the comparison is computed from rbp (new oop)
>> -> the other side is computed from the the spill value (old oop)
>> -> the cmp returns a nonsensical value, and we take the wrong branch
>> -> vectorize even though we have aliasing!
>
> Emanuel Peter has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Apply suggestions from code review
>   
>   Co-authored-by: Manuel Hässig <manuel at haessig.org>
>   Co-authored-by: Christian Hagedorn <christian.hagedorn at oracle.com>

Marked as reviewed by chagedorn (Reviewer).

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

PR Review: https://git.openjdk.org/jdk/pull/27045#pullrequestreview-3176542659