Compiling the ADLC build tool on Windows is generating multiple warnings like
this:
cl : Command line warning D9007 : '/pathmap:' requires
'/experimental:deterministic'; option ignored
This is caused by the `ADLC_CFLAGS` are including `$FILE_MACRO_CFLAGS` but
missing `$REPRODUCIBLE_CFLAGS`.
On Tue, 29 Aug 2023 00:16:46 GMT, Erik Joelsson wrote:
> On Windows, when a directory exists in the "unix" root with the same name as
> a directory in the "test" dir, fixpath will corrupt test arguments to jtreg
> (and possibly other arguments as well). Fixpath sees a string like this:
>
>
On Fri, 1 Sep 2023 15:11:17 GMT, Matthias Baesken wrote:
>> After looking at the build results of a jdk22 build on RHEL 8.4 Linux
>> ppc64le that uses a ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0
>> devkit we observed those unwanted paths in libsplashscreen.so .
>> See those
> After looking at the build results of a jdk22 build on RHEL 8.4 Linux ppc64le
> that uses a ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0
> devkit we observed those unwanted paths in libsplashscreen.so .
> See those objdump and ldd output :
>
> objdump -x ./lib/libsplashscreen.so |
On Fri, 1 Sep 2023 13:39:58 GMT, Matthias Baesken wrote:
>> make/autoconf/lib-x11.m4 line 90:
>>
>>> 88: fi
>>> 89: # Also remove the -R setting for devkit usage
>>> 90: if test "x$with_devkit" != "x" && test "x$with_devkit" != "xno";
>>> then
>>
>> This should rather check if
On Fri, 1 Sep 2023 12:54:45 GMT, Erik Joelsson wrote:
>> After looking at the build results of a jdk22 build on RHEL 8.4 Linux
>> ppc64le that uses a ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0
>> devkit we observed those unwanted paths in libsplashscreen.so .
>> See those objdump
On Fri, 1 Sep 2023 11:02:36 GMT, Matthias Baesken wrote:
> After looking at the build results of a jdk22 build on RHEL 8.4 Linux ppc64le
> that uses a ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0
> devkit we observed those unwanted paths in libsplashscreen.so .
> See those objdump
On 9/1/23 05:24, David Holmes wrote:
On 1/09/2023 6:49 pm, Severin Gehwolf wrote:
On Fri, 2023-09-01 at 12:32 +1000, David Holmes wrote:
Sounds familiar ...
https://bugs.openjdk.org/browse/JDK-8261656 ?
Gives me:
"""
You can't view this issue
"""
Sorry about that - I didn't notice it was
Hello Chen Liang,
The exploded image optimization step runs the newly built JDK (in the
exploded image) to generate data for itself. This means that if you
change something fundamental in the JDK core libraries or the JVM, that
may cause crashes in this build step. To diagnose further, you
On 1/09/2023 6:49 pm, Severin Gehwolf wrote:
On Fri, 2023-09-01 at 12:32 +1000, David Holmes wrote:
Sounds familiar ...
https://bugs.openjdk.org/browse/JDK-8261656 ?
Gives me:
"""
You can't view this issue
"""
Sorry about that - I didn't notice it was not a public issue. Suffice to
say
After looking at the build results of a jdk22 build on RHEL 8.4 Linux ppc64le
that uses a ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0
devkit we observed those unwanted paths in libsplashscreen.so .
See those objdump and ldd output :
objdump -x ./lib/libsplashscreen.so | grep PATH
On Wed, 30 Aug 2023 15:10:45 GMT, Srinivas Vamsi Parasa
wrote:
>>> Hi Vladimir, Just verified that the test/jdk/java/util/Arrays/Sorting.java
>>> is triggering the intrinsic without additional flags
>>
>> Just to add that Sorting.java has short and long run modes. The default when
>> running
On Fri, 2023-09-01 at 12:32 +1000, David Holmes wrote:
> Sounds familiar ...
>
> https://bugs.openjdk.org/browse/JDK-8261656 ?
Gives me:
"""
You can't view this issue
"""
:-(
Thanks,
Severin
Hi Erik, thanks for the fast reply .
I created
https://bugs.openjdk.org/browse/JDK-8315499
Best regards, Matthias
From: erik.joels...@oracle.com
Sent: Thursday, 31 August 2023 15:30
To: Baesken, Matthias ; build-dev@openjdk.org;
sgehwolf
Cc: Zeller, Arno
Subject: Re: [External] : jdk build
On Wed, 30 Aug 2023 03:12:18 GMT, Cesar Soares Lucas
wrote:
> Currently 'make print-targets' print all targets on the same line separated
> by space. That isn't only terribly to read but hard to "grep". Printing each
> target on a separate line seems much better.
>
> Tested on: Linux x64,
On Wed, 30 Aug 2023 16:38:39 GMT, Cesar Soares Lucas
wrote:
>> Currently 'make print-targets' print all targets on the same line separated
>> by space. That isn't only terribly to read but hard to "grep". Printing each
>> target on a separate line seems much better.
>>
>> Tested on: Linux
16 matches
Mail list logo
