Henry Zongaro
Henry Zongaro
Status thus far. The immediate cause of the failure is that a call to [TR_EscapeAnalysis::fixupNode](https://github.com/eclipse-openj9/openj9/blob/999dfbcdc1edaee518235d900f94763dcf16491e/runtime/compiler/optimizer/EscapeAnalysis.cpp#L5424) passes `NULL` as the parent node, as the node that's being fixed up is a...
I went pawing through node n9177n [0xffff49f50440] to see which class was being referenced at that point, as there are seven with that name, some of which have no fields...
The function [candidateHasField](https://github.com/eclipse-openj9/openj9/blob/999dfbcdc1edaee518235d900f94763dcf16491e/runtime/compiler/optimizer/EscapeAnalysis.cpp#L555) is responsible for determining whether a field accesses a field that's actually in a candidate. In particular, I'm looking at these lines: ``` TR_OpaqueClassBlock *fieldClassInCP = fieldSymRef->getOwningMethod(comp)->getClassFromFieldOrStatic(comp,...
I haven't investigated further since last time, but I'll spend some time on it this week. I think I should be able to have a fix ready for JDK 21.
I spent some time producing logs running `TestLoaderLookup.java` locally, just to see whether the circumstances involving instances of `jdk/internal/foreign/abi/AbstractLinker$$Lambda/0x0000000000000000` being allocated and then stored to via a field `AbstractLinker$$Lambda/0x0000000000000000.arg$1` that...
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...
Closing this issue. The bug that ultimately caused the test failure was fixed under pull request #18374. The latent bug in Escape Analysis described in [a comment above](#issuecomment-1708866308) will be...
Reopening as JIT compiler changes are still pending.
Saw a failure with a different symptom in an internal grinder run : ``` 01:02:45 2024-02-13T06:02:19.930075Z 359252 remaining ... 01:02:45 2024-02-13T06:02:20.431950Z 356836 remaining ... 01:02:45 STDERR: 01:02:45 Unhandled exception 01:02:45...
> Any new news on this one? I haven't been able to make further progress on this one.