RFR: 8374521: Support fine-grained native debug levels [v2]

[Aleksey Shipilev]

On Tue, 6 Jan 2026 15:47:31 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

>> [JDK-8374507](https://bugs.openjdk.org/browse/JDK-8374507) forced me to look into debug info sizes again. And I remembered that GCC actually have debug-level support, which can select what kind of diagnostic data is in the debug info. See: https://gcc.gnu.org/onlinedocs/gcc-4.5.0/gcc/Debugging-Options.html
>> 
>> Allowing users to configure the debug level allows two major deviations from the default level (2):
>>  level=1: significantly reduce the debug info size, but still allow backtrace reconstruction
>>  level=3: add even more debugging info, like macro expansion, into the debug data
>> 
>> This RFE upstreams the variant the patch that I have been using in builds.shipilev.net binaries: the fastdebug variants there are done with GCC level=1, greatly optimizing the debug binary sizes, while still maintaining the major benefit of debug binaries -- rich crash diagnostics.
>> 
>> I threw in this option into current GHA builds to conserve more disk space on runners and/or transfers. 
>> 
>> I am open for bikeshedding on the option name :)
>
> Aleksey Shipilev has updated the pull request incrementally with one additional commit since the last revision:
> 
>   --with-debug-info-level

A few more touchups: moved the block to handle both compilers at the same time, stopped issuing `-g2` when default `-g` would do, started to fail when compiler rejects the debug info level requested.

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

PR Comment: https://git.openjdk.org/jdk/pull/29056#issuecomment-3715250904