On Mon, 30 Aug 2021 12:51:43 GMT, Daniel Fuchs wrote:
>> Ioi Lam has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> @dfuch comments
>
> make/jdk/src/classes/build/tools/classlist/SortClasslist.java line 58:
>
>> 56: String
> When the classlist is generated using build.tools.classlist.HelloClasslist,
> its contents may be non-deterministic due to Java thread execution order.
>
> We should sort the generated classlist to make the JDK image's contents more
> deterministic.
>
> Tested with Mach5 tier1, tier2,
On Mon, 30 Aug 2021 13:06:19 GMT, Magnus Ihse Bursie wrote:
> Description from the bug:
>
> When building the JDK and running `configure` the output includes (example):
>
> Build performance summary:
> * Cores to use: 4
> * Memory limit: 32768 MB
>
>
> The "Cores to use" value is
On Mon, 30 Aug 2021 13:06:19 GMT, Magnus Ihse Bursie wrote:
> Description from the bug:
>
> When building the JDK and running `configure` the output includes (example):
>
> Build performance summary:
> * Cores to use: 4
> * Memory limit: 32768 MB
>
>
> The "Cores to use" value is
Hi all,
There is an open request[1] to bump the minimum GCC version from 5 to 6.
We've traditionally been very conservative with supporting old GCC
versions, but GCC 6 was released in 2016 (compared to GCC 5 in 2015),
and I think this sounds conservative enough.
Would it create a lot of
Description from the bug:
When building the JDK and running `configure` the output includes (example):
Build performance summary:
* Cores to use: 4
* Memory limit: 32768 MB
The "Cores to use" value is misleading; it is not actually the number of cores
specified using `--with-num-cores`,
On Fri, 27 Aug 2021 23:12:52 GMT, Ioi Lam wrote:
> When the classlist is generated using build.tools.classlist.HelloClasslist,
> its contents may be non-deterministic due to Java thread execution order.
>
> We should sort the generated classlist to make the JDK image's contents more
>
On Fri, 27 Aug 2021 14:28:07 GMT, Magnus Ihse Bursie wrote:
> Having the environment variable CLASSPATH set when building can cause
> hard-to-diagnose build errors. We should not silently accept the CLASSPATH
> variable when building. Normally, the classpath should be correctly setup for
>
On Fri, 27 Aug 2021 23:12:52 GMT, Ioi Lam wrote:
> When the classlist is generated using build.tools.classlist.HelloClasslist,
> its contents may be non-deterministic due to Java thread execution order.
>
> We should sort the generated classlist to make the JDK image's contents more
>
