-
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
Extend arraycmp length child #19332
Extend arraycmp length child #19332
Conversation
989b2d8
to
fcc1338
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to the review comments, I noticed there is code in CICSTransform2ArrayCmpIfs
that still seems to be using a 32-bit length for an arraycmplen
.
Change all uses of arraycmp to take a 64 bit length child instead of 32 bits. Signed-off-by: Spencer Comin <spencer.comin@ibm.com>
fcc1338
to
3cca085
Compare
Ran some internal tests. I saw a couple failures, but the failures look unrelated to me. JDK21 tests:https://hyc-runtimes-jenkins.swg-devops.com/job/Pipeline-Build-Test-Personal/22751/ x86-64_linux sanity.functional failure:
s390x_linux sanity.system failure:
JDK8 vmfarm tests:http://vmfarm.rtp.raleigh.ibm.com/build_info.php?build_id=72852
|
As a note, this PR must be merged in coordination with reverting the 64-bit |
@Spencer-Comin, may I ask you to open the new PR to reapply eclipse-omr/omr#7313? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks!
Done! eclipse-omr/omr#7388 |
Jenkins test sanity.functional,sanity.openjdk all jdk8,jdk11,jdk17,jdk21 depends eclipse-omr/omr#7388 |
xLinux failures appear to be infrastructure-related. Rerunning. The runs that are listed as "pending" appear to have actually aborted. I'll rerun those as well. The JDK 21 sanity.openjdk s390x Linux failures appear to be due to #18908. That issue had been closed recently as it couldn't be reproduced any longer. Jenkins test sanity.functional,sanity.openjdk xlinunux jdk8,jdk11,jdk21 depends eclipse-omr/omr#7388 |
Fixing the typo: Jenkins test sanity.functional,sanity.openjdk xlinux jdk8,jdk11,jdk21 depends eclipse-omr/omr#7388 |
Jenkins test sanity.openjdk xlinux jdk17 depends eclipse-omr/omr#7388 |
Jenkins test sanity.functional,sanity.openjdk win jdk8,jdk11,jdk17 depends eclipse-omr/omr#7388 |
Jenkins test sanity.openjdk win jdk21 depends eclipse-omr/omr#7388 |
Jenkins test sanity.functional,sanity.openjdk aix jdk21 depends eclipse-omr/omr#7388 |
There are some build failures in JDK 21 builds for aix, xLinux and x86-64 Windows. Two of them appear to be happening during Value Propagation - I haven't looked into the third. I looked at a jitdump for the Windows failure, and there didn't appear to be any @Spencer-Comin, may I ask you to take a look at these build failures to determine whether they could be in any way related to your pull requests? |
@Spencer-Comin, it looks like OMR acceptance builds are hitting this same problem. For instance, see https://openj9-jenkins.osuosl.org/view/Build_OMR/job/Build_JDK21_ppc64_aix_OMR/140/consoleFull |
Looking at some of the other failures, there are some infrastructure-related problems, but others appear to be similar to the failures we saw JDK 21 testing. Once those problems have been resolved, I'll rerun the testing. |
I looked into the windows failures and reran the jdk11 sanity.functional (https://hyc-runtimes-jenkins.swg-devops.com/job/Pipeline-Build-Test-Personal/22949/) (branches rebased to more recent openj9/omr). I also ran a control test without my changes (https://hyc-runtimes-jenkins.swg-devops.com/job/Pipeline-Build-Test-Personal/22950/). The failing tests are the same between my changes and the control. |
Right - thanks for looking at that. I should have clarified earlier that because we're seeing similar failures with the OMR Acceptance builds, the failures are almost certainly unrelated to your changes. Those failures are still under investigation. Once they're resolved, I'll rerun testing on your changes. In the meanwhile, those failures are creating too much noise to feel entirely safe about merging your changes. |
Most of the failures we were seeing were caused by unrelated changes and should now be resolved. Rerunning testing, as this will require a coordinate merge. Jenkins test sanity.functional,sanity.openjdk all jdk8,jdk11,jdk17,jdk21 depends eclipse-omr/omr#7388 |
Restarting AIX test runs that were aborted: Jenkins test sanity.functional,sanity.openjdk aix jdk8,jdk11 depends eclipse-omr/omr#7388 |
Jenkins test sanity.openjdk aix jdk17 depends eclipse-omr/omr#7388 |
JDK 8 x86-64 macOS sanity.functional test failure looks like an infrastructure problem. Rerunning: Jenkins test sanity.functional xmac jdk8 depends eclipse-omr/omr#7388 |
JDK 17 sanity.functional aix testing looks like it was aborted. Rerunning. Looking through the failures on other platforms, they all appear to be due to known issues:
Jenkins test sanity.functional aix jdk17 depends eclipse-omr/omr#7388 |
There are only two AIX machines left functioning atm. I removed AIX from nightly builds, but not the weekend testing. You might be able to get a PR build through once the weekend testing finishes or times out. |
Despite the problem running the AIX JDK 17 sanity.functional testing, I think this change and the change in OMR on which it depends have been well exercised. Merging. |
Change all uses of arraycmp to take a 64 bit length child instead of 32 bits.
Relies on eclipse-omr/omr#7313