Re: RFR: 8326509: Clean up JNIEXPORT in Hotspot after JDK-8017234 [v3]

2024-02-24 Thread Martijn Verburg
On Sat, 24 Feb 2024 20:00:34 GMT, Martijn Verburg wrote: >> Personally I have never used `das`/`das1` on any AArch64 port when >> debugging. I guess it was somewhat handy when the backend was originally >> developed. I would argue that the built-in disassembler of any debugger and >> `disnm`

Re: RFR: 8326509: Clean up JNIEXPORT in Hotspot after JDK-8017234 [v3]

2024-02-24 Thread Martijn Verburg
On Fri, 23 Feb 2024 12:03:37 GMT, Bernhard Urban-Forster wrote: >> Instead of discussing removal of windows/aarch64 (although the general rule >> in OpenJDK is that ports that are not maintained by anyone should be >> removed); let's stick to the question here: do we need to export `das1()` >

Re: RFR: 8174269: Remove COMPAT locale data provider from JDK

2024-02-24 Thread Andrey Turbanov
On Fri, 23 Feb 2024 21:24:10 GMT, Naoto Sato wrote: > This PR intends to remove the legacy `COMPAT` locale data from the JDK. The > `COMPAT` locale data was introduced for applications' migratory purposes > transitioning to `CLDR`. It is becoming a technical debt and now is the time > to remov

Re: RFR: 8326587: Separate out Microsoft toolchain linking

2024-02-24 Thread Magnus Ihse Bursie
On Sat, 24 Feb 2024 06:20:54 GMT, Julian Waters wrote: > Why not reuse the AR variable for lib rather than introduce an entirely new > LIB variable? The reason will become more apparent as I progress towards proper handling of static libs. In short, AR is not by far a 1-to-1 mapping with LIB.

Re: RFR: 8174269: Remove COMPAT locale data provider from JDK

2024-02-24 Thread Alan Bateman
On Fri, 23 Feb 2024 21:24:10 GMT, Naoto Sato wrote: > This PR intends to remove the legacy `COMPAT` locale data from the JDK. The > `COMPAT` locale data was introduced for applications' migratory purposes > transitioning to `CLDR`. It is becoming a technical debt and now is the time > to remov