On Fri, 5 Nov 2021 17:31:50 GMT, Naoto Sato wrote:
> Please review the subject fix. In light of JEP400, Java runtime can/should
> start in UTF-8 charset if the underlying native encoding is not supported.
If this issue is not a part of JEP-400, I think UTF_8 may not be only solution
for sun/ni
On Sun, 1 Aug 2021 22:01:33 GMT, Markus KARG wrote:
>> This PR-*draft* is **work in progress** and an invitation to discuss a
>> possible solution for issue
>> [JDK-8265891](https://bugs.openjdk.java.net/browse/JDK-8265891). It is *not
>> yet* intended for a final review.
>>
>> As proposed in
On Mon, 4 Oct 2021 21:13:02 GMT, PROgrm_JARvis wrote:
> This is trivial fix of
> [JDK-8274686](https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8274686)
> which replaces manually-computed `int`-based `long` hash-code.
>
> Because `Long#hashCode(long)` uses other hashing function than t
On Fri, 29 Oct 2021 16:32:43 GMT, Mandy Chung wrote:
> The change looks okay. My suggestion is to get 1-6 all ready to push around
> the same time. It's okay to have separate JBS issues and PRs.
ok, I'll continue to work using the plan from the description.
-
PR: https://git.openj
On Fri, 5 Nov 2021 17:31:50 GMT, Naoto Sato wrote:
> Please review the subject fix. In light of JEP400, Java runtime can/should
> start in UTF-8 charset if the underlying native encoding is not supported.
The same rationale as JEP 400, that UTF-8 is the de-facto encoding these days.
This is fo
Hello Ioi,
On 02/11/21 12:13 am, Ioi Lam wrote:
Hi Jaikiran,
Thanks for writing the test case to explore the problems in this area.
Please see my comments below:
...
Generally speaking, CDS has two levels of archiving:
[1] archiving class metadata -- classes in the
$JAVA_HOME/lib/classlist
