On Tue, 10 Feb 2026 11:37:53 GMT, Thomas Stuefe <[email protected]> wrote:

>> _This patch is not intended for JDK 26_. 
>> 
>> *updated description 2026-02-13*
>> 
>> This change removes the uncompressed Klass pointer mode and, with compressed 
>> Klass pointers remaining as the only option, the 
>> `UseCompressedClassPointers` switch.
>> 
>> For motivation, please take a look at CSR associated with the deprecation 
>> (which we did for JDK 25) and the preparatory discussion we had at the start 
>> of the year around this topic [2].
>> 
>> This patch is quite invasive and touches many parts of the JVM, since its 
>> goal is to remove most traces of the uncompressed Klass path and to take 
>> advantage of opportunities for simplification. In some cases, I did not take 
>> opportunities for further simplification to keep the patch somewhat legible; 
>> it will be onerous enough to review.
>> 
>> ### Implementation Notes
>> 
>> With uncompressed Klass pointers removed, we have three modes of operation 
>> left (including 32-bit):
>>   a) 64-bit, COH off - this is the old `+UseCompressedClassPointers` mode. 
>> This is now the standard mode until we run with COH by default.
>>   b) 64-bit, COH on
>>   c) 32-bit - Here, we run with a "fake" narrow Klass pointer mode. We run 
>> with hardcoded narrowKlass base == NULL and shift = 0, so nKlass == Klass*. 
>> The difference to (a, b) is that we don't use a class space. Most of this 
>> was implemented with JDK-8363998 [3] - here, we just add a compile-time 
>> switch `INCLUDE_CLASSSPACE`, which is true on 32-bit, false on 64-bit.
>> 
>> I ensured *arm32* builds and I performed some rudimentary checks (selected 
>> metaspace/gc tests, and a simple Spring PetClinic run). Vendors with an 
>> interest in arm32 will have to step up and do their own, more thorough unit 
>> testing. Also, I did not see anyone doing follow-up work after JDK-8363998 
>> [3] - so some issues may still lurk from that patch as well (but maybe 
>> JDK-8363998 was just not breaking anything).
>> 
>> I did not check *zero 32-bit*, the only other platform supporting 32-bit. 
>> Anyone with an interest in 32-bit zero should chip in.
>>   
>> Pre-existing errors: While working on this patch, I stumbled over a few 
>> occurrences of old but benign bugs. Mostly old code assuming 
>> CompressedClassPointers and CompressedOops were still tied together 
>> (example: Arguments::set_heap_size()). These bugs are implicitly fixed with 
>> this patch.
>> 
>> ### Testing
>> 
>> - tier 1 2 3 locally on Linux x64
>> - SAP ran their whole set of tests for all the platforms they support.
>> 
>> 
>> [1] https://bugs.openjdk.org/browse/JDK-8350754
>> [2] https://...
>
> Thomas Stuefe has updated the pull request incrementally with one additional 
> commit since the last revision:
> 
>   Replace Metaspace::using_class_space with define

I have reviewed all CPU specific code, and a bunch of shared code (but not 
all), and so far looks great. I only have one small and unrelated question.

src/hotspot/share/cds/filemap.cpp line 1908:

> 1906:   aot_log_info(aot)("The %s was created with UseCompressedOops = %d, 
> UseCompactObjectHeaders = %d",
> 1907:                           file_type, compressed_oops(), 
> compact_headers());
> 1908:   if (compressed_oops() != UseCompressedOops) {

Unrelated to your change, but does COH need to be checked here also?

-------------

PR Review: https://git.openjdk.org/jdk/pull/28366#pullrequestreview-3890476762
PR Review Comment: https://git.openjdk.org/jdk/pull/28366#discussion_r2884732819

Reply via email to