Re: RFR: 8322936: Update blessed-modifier-order.sh for default, sealed, and non-sealed

2024-01-03 Thread Martin Buchholz
On Wed, 3 Jan 2024 12:09:42 GMT, Pavel Rappo wrote: > Please review this PR to update `blessed-modifier.order.sh` for the > `default`, `sealed`, `non-sealed`, and `strictfp` modifiers. > > In a [discussion][] preceding this PR, it was agreed that the script should > better refer to relevant

Re: RFR: 8322936: Update blessed-modifier-order.sh for default, sealed, and non-sealed

2024-01-03 Thread Martin Buchholz
On Wed, 3 Jan 2024 17:39:56 GMT, Pavel Rappo wrote: >> bin/blessed-modifier-order.sh line 34: >> >>> 32: echo >>> 33: echo "See:" >>> 34: echo >>> "https://docs.oracle.com/javase/8/docs/api/java/lang/reflect/Modifier.html#toString-int-; >> >> Looking at the latest docs for

Re: RFR: 8309130: x86_64 AVX512 intrinsics for Arrays.sort methods (int, long, float and double arrays) [v42]

2024-01-03 Thread Eric Murphy
On Sun, 15 Oct 2023 07:40:06 GMT, himichael wrote: > sing a physical machine, I am using a virtual machine, this virtual machine > supports the AVX512 instruction set. > How do I open libsimdsort ? @himichael Did you ever resolve your issue? I am using JDK22 from SDKMan and have the same

Re: OpenJDK11 build on macOS with autoconf 2.72 / -std=gnu++11 option

2024-01-03 Thread Kim Barrett
> On Jan 3, 2024, at 7:16 AM, Baesken, Matthias > wrote: > > Btw. I found this rather recent discussion about reverting the forcing > of setting -std=gnu++11 in autoconf : > >

Integrated: 8322873: Duplicate -ljava -ljvm options for libinstrument

2024-01-03 Thread Mikael Vidstedt
On Tue, 2 Jan 2024 21:44:04 GMT, Mikael Vidstedt wrote: > The libinstrument library is linked against libjava and libjvm, twice. This > is mostly harmless but Xcode 15.x generates a warning: > > Creating support/modules_libs/java.instrument/libinstrument.dylib from 12 > file(s) > ld: warning:

Re: RFR: 8322873: Duplicate -ljava -ljvm options for libinstrument

2024-01-03 Thread Mikael Vidstedt
On Tue, 2 Jan 2024 21:44:04 GMT, Mikael Vidstedt wrote: > The libinstrument library is linked against libjava and libjvm, twice. This > is mostly harmless but Xcode 15.x generates a warning: > > Creating support/modules_libs/java.instrument/libinstrument.dylib from 12 > file(s) > ld: warning:

Re: RFR: 8322936: Update blessed-modifier-order.sh for default, sealed, and non-sealed

2024-01-03 Thread Pavel Rappo
On Wed, 3 Jan 2024 17:16:37 GMT, Martin Buchholz wrote: > it also needs a corresponding update > https://download.java.net/java/early_access/jdk23/docs/api/java.base/java/lang/reflect/Modifier.html#toString(int) >From the preceding discussion, it follows that it cannot be done:

Re: RFR: 8322936: Update blessed-modifier-order.sh for default, sealed, and non-sealed

2024-01-03 Thread Martin Buchholz
On Wed, 3 Jan 2024 12:09:42 GMT, Pavel Rappo wrote: > Please review this PR to update `blessed-modifier.order.sh` for the > `default`, `sealed`, `non-sealed`, and `strictfp` modifiers. > > In a [discussion][] preceding this PR, it was agreed that the script should > better refer to relevant

Re: RFR: 8322936: Update blessed-modifier-order.sh for default, sealed, and non-sealed

2024-01-03 Thread Roger Riggs
On Wed, 3 Jan 2024 12:09:42 GMT, Pavel Rappo wrote: > Please review this PR to update `blessed-modifier.order.sh` for the > `default`, `sealed`, `non-sealed`, and `strictfp` modifiers. > > In a [discussion][] preceding this PR, it was agreed that the script should > better refer to relevant

Re: RFR: 8322936: Update blessed-modifier-order.sh for default, sealed, and non-sealed

2024-01-03 Thread Erik Joelsson
On Wed, 3 Jan 2024 12:09:42 GMT, Pavel Rappo wrote: > Please review this PR to update `blessed-modifier.order.sh` for the > `default`, `sealed`, `non-sealed`, and `strictfp` modifiers. > > In a [discussion][] preceding this PR, it was agreed that the script should > better refer to relevant

Re: RFR: 8322873: Duplicate -ljava -ljvm options for libinstrument

2024-01-03 Thread Erik Joelsson
On Tue, 2 Jan 2024 21:44:04 GMT, Mikael Vidstedt wrote: > The libinstrument library is linked against libjava and libjvm, twice. This > is mostly harmless but Xcode 15.x generates a warning: > > Creating support/modules_libs/java.instrument/libinstrument.dylib from 12 > file(s) > ld: warning:

Re: RFR: JDK-8320458: Improve structural navigation in API documentation [v2]

2024-01-03 Thread Hannes Wallnöfer
> This is a rather big change to update the structural navigation in API > documentation generated by JavaDoc. It adds a table of contents for the > current page to module, package, and class documentation, and replaces the > old sub-navigation bar with a breadcrumb-style links in those pages.

RE: OpenJDK11 build on macOS with autoconf 2.72 / -std=gnu++11 option

2024-01-03 Thread Baesken, Matthias
Btw. I found this rather recent discussion about reverting the forcing of setting -std=gnu++11 in autoconf : https://mail.gnu.org/archive/html/bug-autoconf/2023-12/msg00073.html https://savannah.gnu.org/support/?110879 revert forcing/setting -std=gnu++11 by default (introduced in

RFR: 8322936: Update blessed-modifier-order.sh for default, sealed, and non-sealed

2024-01-03 Thread Pavel Rappo
Please review this PR to update `blessed-modifier.order.sh` for the `default`, `sealed`, `non-sealed`, and `strictfp` modifiers. In a [discussion][] preceding this PR, it was agreed that the script should better refer to relevant JLS sections rather than to

Re: RFR: 8322873: Duplicate -ljava -ljvm options for libinstrument

2024-01-03 Thread Julian Waters
On Tue, 2 Jan 2024 21:44:04 GMT, Mikael Vidstedt wrote: > The libinstrument library is linked against libjava and libjvm, twice. This > is mostly harmless but Xcode 15.x generates a warning: > > Creating support/modules_libs/java.instrument/libinstrument.dylib from 12 > file(s) > ld: warning:

Re: OpenJDK11 build on macOS with autoconf 2.72 / -std=gnu++11 option

2024-01-03 Thread Julian Waters
> So why is "-std=gnu++11" being used at all? autoconf has a heuristic that automatically checks "For compiler flags required to enable C++11 for the current compiler", and if the check passes, autoconf automatically adds -std=gnu++11 to the CFLAGS. Something is likely (wrongly) tripping this