[lworld] Integrated: 8280707: [lworld] More issues with C2's arraycopy intrinsic

[Tobias Hartmann]

On Thu, 27 Jan 2022 15:15:04 GMT, Tobias Hartmann <thartmann at openjdk.org> wrote:

> The memory output of the `MemBarCPUOrder` node added to prevent writes into the source from floating below the arraycopy is not correctly wired. As a result, we hit an "dependence cycle found" assert in GCM. I also removed a comment in that code that was already removed from mainline.
> 
> In `TypeAryPtr::add_field_offset_and_offset` we set the wrong offset if the field is not found in a flat array (for example, because the inline type has no fields). This leads to an assert in the matcher due to an unexpected address type change.
> 
> Thanks,
> Tobias

This pull request has now been integrated.

Changeset: 22b271d0
Author:    Tobias Hartmann <thartmann at openjdk.org>
URL:       https://git.openjdk.java.net/valhalla/commit/22b271d0b3db95f914b9f8abb9eeb04169c1e05a
Stats:     93 lines in 3 files changed: 75 ins; 14 del; 4 mod

8280707: [lworld] More issues with C2's arraycopy intrinsic

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

PR: https://git.openjdk.java.net/valhalla/pull/620