-
Notifications
You must be signed in to change notification settings - Fork 738
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JDK21 jdk_foreign_0_FAILED java/foreign/loaderLookup/TestLoaderLookup.java NPE at java.base/jdk.internal.foreign.abi.AbstractLinker.stripNames(AbstractLinker.java:278) #18142
Comments
@ChengJin01 Please take a look |
which was totally in JIT
Based on the findings, I'd like the JIT team get involved to see what happened to their code as I suspect the two issues (#18142 and #18074 belong to the same problem). |
Thanks, @ChengJin01. I'll take a look at it. |
I have verified that this is another instance of #18074. From a jitdump from a grinder run, Escape Analysis is transforming a store to the field of a lambda
to this
The indirect store through an address of zero is the transformation that Escape Analysis performs if it thinks the field — One thing that I notice is that the |
Using the fix in #18374, 100X Grinder of TestLoaderLookup.java and 100X Grinder running jdk_foreign_0 all passed. The behaviour seen in Esape Analysis is also caused by the incorrect symref sharing of hidden class field shadows. #18374 addresses this incorrect symref sharing. |
The problem with recognizing whether fields in hidden classes are the same was fixed by pull request #18374. That bug resulted in trees that expose the latent bug in Escape Analysis that resulted in the |
@hzongaro, is any update with this issue in JIT? |
The problem that ultimately led to the test failure was fixed by pull request #18374. I've kept this bug open because that problem exposed another bug in Escape Analysis that is still present. However, it's unlikely that it will be seen. If you're still seeing failures related to If my leaving this issue open is causing any confusion, I can close it and then open a new issue to track the latent Escape Analysis bug that I mentioned. |
@hzongaro, many thanks for your clarification on this issue. I think i should be preferable to close this issue given the failure with |
As @ChengJin01 suggested, I will close this issue, which was fixed by pull request #18374, and I will track the clean up work for Escape Analysis under issue #19148. |
Failure link
From an internal build(
cent8-aarch64-2
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - 17/50 failed
The text was updated successfully, but these errors were encountered: