RFR: 8300255: Introduce interface for GC oop verification in the assembler

Martin Doerr mdoerr at openjdk.org
Tue Feb 7 11:55:41 UTC 2023


On Tue, 7 Feb 2023 05:14:17 GMT, Martin Doerr <mdoerr at openjdk.org> wrote:

>> PPC code contributed by @TheRealMDoerr and RISC-V code contributed by @yadongw. Could you please check that it works on your machines?
>
>> PPC code contributed by @TheRealMDoerr and RISC-V code contributed by @yadongw. Could you please check that it works on your machines?
> 
> The default version of check_oop doesn't work for ZGC. I suggest to exclude the PPC64 parts here and ship them with the generational ZGC PR. That will reduce effort. Does that make sense?

> > > PPC code contributed by @TheRealMDoerr and RISC-V code contributed by @yadongw. Could you please check that it works on your machines?
> > 
> > 
> > The default version of check_oop doesn't work for ZGC. I suggest to exclude the PPC64 parts here and ship them with the generational ZGC PR. That will reduce effort. Does that make sense?
> 
> Hmm. Looking at the changes of this patch, we used to call __ verify_oop, but now we call check_oop on the barrier set assembler, which in turn has a single implementation which calls __ verify_oop. It seems like this patch currently does not change the behaviour at all to what happened before? While I am perfectly fine removing the PPC changes, I don't think I understand what behaviour this patch changes for PPC.

You're right. VerifyOops is already broken with ZGC on PPC64. You can keep the PPC64 parts as they are. The generational ZGC code will fix the problem. So, I'm fine with this PR.

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

PR: https://git.openjdk.org/jdk/pull/12443


More information about the hotspot-dev mailing list