On Wed, 13 Sep 2023 23:02:21 GMT, Srinivas Vamsi Parasa
wrote:
> Could you please have a look at the changes in `DualPivotQuicksort.java` and
> provide your feedback?
I agree that is much cleaner, glad that worked out. That neatly covers multiple
element types and Java-based insertion sort
On Tue, 12 Sep 2023 21:57:31 GMT, Justin Lu wrote:
> JDK .properties files still use ISO-8859-1 encoding with escape sequences. It
> would improve readability to see the native characters instead of escape
> sequences (especially for the L10n process). The majority of files changed
> are
On Thu, 14 Sep 2023 14:07:20 GMT, Adam Farley wrote:
> While building openjdk on aix, we see this build-fail error:
>
> The fopen system call failed on file
> -f/home/.etce4tcetc./_BUILD_LIBJDWP_objectfilenames.txt
>
> This change expands the fix for the similar issue on macosx, and
While building openjdk on aix, we see this build-fail error:
The fopen system call failed on file
-f/home/.etce4tcetc./_BUILD_LIBJDWP_objectfilenames.txt
This change expands the fix for the similar issue on macosx, and prevents the
fopen issue on aix.
-
Commit messages:
-
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:
>
>
Perhaps we could direct developers to look for the *** Waiting for
unfinished jobs message in build.log as well, since that typically
occurs extremely close to the error site?
Also, hi Magnus! It's been quite a while! :D
best regards,
Julian
On 2023-09-13 16:14, Baesken, Matthias wrote:
I found the "] Error " - advice unfortunately AFTER I did some
searching through the log (seems I overlooked it at first because I
searched for a compile errors and not for such “hints” ) .
But in this case it worked , so my idea was - why
On Wed, 13 Sep 2023 18:18:53 GMT, Kim Barrett wrote:
> It seems to be complaining about atomic increment of a data member, which is
> really weird.
>
> ```
> Atomic::add(&_claimed, flushed);
> ```
>
> When we saw this warning in other places it was because we were passing a
> pointer that
