On Fri, 29 May 2026 16:25:36 GMT, Jatin Bhateja <[email protected]> wrote:
>> @jatin-bhateja the main push back is not the existing good work that has >> been done, I am very pleased with the outcome and how you managed to >> separate out the work, all this reduces the risk, makes it easier to review, >> and increases the quality. >> >> The push back is the risk of there being bugs introduced in HotSpot after >> RDP1, and those take time to emerge (over the large test matrix for HotSpot) >> and they become increasingly expensive to fix as we get closer to the >> release. Further, fixing such issues takes time away from other important >> work. What we need is time, and unfortunately we don't have it for 27, we do >> for 28. >> >> I approved this from a libraries perspective, but from a HotSpot perspective >> the compiler folks are right. Quan makes a very good point about raising >> the bar, and Emanuel has been consistently doing so in careful reviews and >> increasing test coverage. >> >> So let's target 28. My recommendation is to push soon after RDP1 to mainline >> and follow up quickly with the fuzzer PR, then we have a good period time >> for testing and fixing issues the fuzzer may find or other tests may find >> (such as tests run in lower tiers with HotSpot under stress). > >> >> So let's target 28. My recommendation is to push soon after RDP1 to mainline >> and follow up quickly with the fuzzer PR, then we have a good period time >> for testing and fixing issues the fuzzer may find or other tests may find >> (such as tests run in lower tiers with HotSpot under stress). > > Hi @PaulSandoz , > Thanks for the clear direction. Will do — I'll integrate this patch next > week, soon after the JDK 27 RDP1 fork, and then work closely with @eme64 on > the fuzzer (#30997), since he architected that tool. > Hi @xuemingshen-oracle , > All your comments have been addressed; looking forward to your approval. > Best Regards @jatin-bhateja I'll help with compiler review/approval, so we can integrate right after the fork/branch to JDK28 :) ------------- PR Comment: https://git.openjdk.org/jdk/pull/28002#issuecomment-4583124732
