On Tue, 11 Aug 2026 14:18:12 GMT, Ashay Rane <[email protected]> wrote:
> Thanks also for your note about precompiled headers. In the numbers that I > posted, the first build has always been with caching enabled (whether through > ccache or sccache) and with precompiled headers disabled. I see your point > that disabling precompiled headers would provide a misleading baseline. > > Let me do two things. First, I'll mark this PR as Draft until I can gather > more measurements across different platforms with and without precompiled > headers and after disabling caching (it might take me a few days). And > second, let me do some cursory inspection to find why ccache sees the cl > compiler invocations as uncacheable. No need. I was just curious. Further measurements are not a requirement for integrating this. This is all opt in and each user will need to decide for themselves what tradeoffs they are willing to make to get optimal performance for their workflows. > At the risk of veering off on a tangent, is there an appetite for making the > build use generators like CMake or Meson (to make the build both fast/native > and easier to port across platforms)? I know that the existing Make-based > build is an acute problem only on Windows, thus increasing the inertia for > change, but I wonder if this has been discussed before. Introducing the configure script and redesigning the makefiles in the build-infra project back in JDK 8 was a huge step forward in speeding up the build, while unfortunately not optimal for Windows. At this time there are no plans for rewriting the OpenJDK build further. I personally have very little experience with CMake, but from what I understand, we would trade one set of problems for another, as such systems tend to be quite opinionated, and we would likely end up butting against those opinions quite a lot, as we also tend to be rather opinionated. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32059#issuecomment-5256805806
