Henry Zongaro

I was never able to reproduce the failure in grinder runs with x86-64_mac, aarch64_mac or x86-64_windows — only s390x_linux. However, the failures for s390x_linux seem to have disappeared after ibmruntimes/openj9-openjdk-jdk21#132...

@nbhuiyan, may I ask you to take a look at this problem?

I'm having some difficulty matching up the contents of one of the `jitdump` files that was produced with one of the `core` files, so I'm trying another [internal grinder run](https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/39223/)...

I was able to reproduce this running locally on a ppc64le Linux system. It might be AOT-related. I'll spend some time trying to narrow things down.

> Any new news on this one? I haven't been able to spend further time on this one recently.

> @hzongaro how can I know the status of the issue? Sorry - I missed your last message, @singh264. I haven't had a chance to investigate this one further. I'll...

@a7ehuo, may I ask you to look at this failure? I will share in Box a build and tests that I had used to reproduce the problem.

> Math.max/min call nodes are transformed to a functionally equivalent tree that uses fmax/fmin/dmax/dmin One oddity about `java.lang.Math.{max|min}({double|float})` is in the treatment of negative zero: > Unlike the numerical comparison...

Jenkins test sanity all jdk8,jdk11,jdk17,jdk21

Looks like at least some of the build failures are real. For example, from the [JDK 11 PPC64LE](https://openj9-jenkins.osuosl.org/job/Build_JDK11_ppc64le_linux_Personal/604/consoleFull) build: ``` 17:57:09 __kernel_sigtramp_rt64+0x0 (0x0000100000050478) 17:57:09 _ZN9TR_Memory19allocateStackMemoryEmN13TR_MemoryBase10ObjectTypeE+0x28 (0x00001000016CAF58 [libj9jit29.so+0x6daf58]) 17:57:09 _ZN15TR_VMFieldsInfoC1EPN2TR11CompilationEP7J9Classi17TR_AllocationKind+0x114 (0x0000100001217C84...