RFR: 8324050: Issue store-store barrier after re-materializing objects during deoptimization
Andrew Haley
aph at openjdk.org
Tue Jan 23 12:25:35 UTC 2024
On Mon, 22 Jan 2024 21:06:17 GMT, Vladimir Kozlov <kvn at openjdk.org> wrote:
> > This seems similar to [a recent discussion](https://mail.openjdk.org/pipermail/hotspot-compiler-dev/2024-January/071521.html). There, it is decided that a release barrier would be safer. Should we do it similarly here? Thanks.
>
> I think, if decided, it should be done in separate RFE uniformly in all places: Interpreter, C1, C2 and here in deoptimization code.
That would be the wrong thing to do, because the risk that leads us (possibly? - discuss) to need release can only happen in an optimizing compiler. AFAIK...
-------------
PR Comment: https://git.openjdk.org/jdk/pull/17503#issuecomment-1905949873
More information about the hotspot-dev
mailing list