On Wed, 9 Apr 2025 20:26:13 GMT, Chris Plummer wrote:
> > Making hotspot `-Os` would certainly never make any sense, for example.)
>
> When the minimalVM was first created, there was a quite of bit of
> benchmarking done to decide which hotspot files to build with -Os and which
> to build with
On Thu, 10 Apr 2025 05:50:23 GMT, Serguei Spitsyn wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause pro
On Mon, 11 Nov 2024 09:51:35 GMT, Julian Waters wrote:
>> After 8339120, gcc began catching many different instances of unused code in
>> the Windows specific codebase. Some of these seem to be bugs. I've taken the
>> effort to mark out all the relevant globals and locals that trigger the
>> u
On Thu, 10 Apr 2025 05:50:23 GMT, Serguei Spitsyn wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause pro
On Thu, 10 Apr 2025 09:20:58 GMT, Joel Sikström wrote:
>>> Note that any reference to pages from here on out refers to the concept of
>>> a heap region in ZGC, not pages in the operating system (OS), unless stated
>>> otherwise.
>>
>> # Background
>>
>> This PR addresses fragmentation by intr
>> Note that any reference to pages from here on out refers to the concept of a
>> heap region in ZGC, not pages in the operating system (OS), unless stated
>> otherwise.
>
> # Background
>
> This PR addresses fragmentation by introducing a Mapped Cache that replaces
> the Page Cache in ZGC. T
On Thu, 10 Apr 2025 09:20:58 GMT, Joel Sikström wrote:
>>> Note that any reference to pages from here on out refers to the concept of
>>> a heap region in ZGC, not pages in the operating system (OS), unless stated
>>> otherwise.
>>
>> # Background
>>
>> This PR addresses fragmentation by intr
On Thu, 10 Apr 2025 09:16:56 GMT, Joel Sikström wrote:
>>> Note that any reference to pages from here on out refers to the concept of
>>> a heap region in ZGC, not pages in the operating system (OS), unless stated
>>> otherwise.
>>
>> # Background
>>
>> This PR addresses fragmentation by intr
On Thu, 10 Apr 2025 07:32:18 GMT, Magnus Ihse Bursie wrote:
>> You don't have to do that, I'm working on an omnibus UTF-8 fixing PR right
>> now, where I will include a fix for this as well.
>
> If anything, I might be a bit worried that there are more incorrect
> conversions stemming from this
On Thu, 10 Apr 2025 02:13:46 GMT, Fei Yang wrote:
> > qemu-user, "uarch: qemu" in cpuinfo: `[0.084s][info ][os,cpu] CPU: total 28
> > (initial active 28) qemu rv64 rvi rvm rva rvf rvd rvc rvv zba zbb zbs zfh
> > zfhmin zvbc zvfh zicond` Hence we know this is qemu-user (only qemu-user
> > sets
On Thu, 10 Apr 2025 08:08:02 GMT, Eirik Bjørsnøs wrote:
>> If anything, I might be a bit worried that there are more incorrect
>> conversions stemming from this PR, that my automated tools and manual
>> scanning has not revealed.
>
> Some observations:
>
> 1: This PR seems to have been abondo
On Wed, 13 Sep 2023 17:38:28 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 l
On Wed, 13 Sep 2023 17:38:28 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 l
On Thu, 10 Apr 2025 07:31:37 GMT, Magnus Ihse Bursie wrote:
>> Right, that `å` looks to have been incorrectly converted during the
>> ISO-8859-1 to UTF-8 conversion. (I can't find the script used for conversion
>> as this change is from some time ago.)
>>
>> Since the change occurs in a commen
On Wed, 9 Apr 2025 20:38:08 GMT, Chris Plummer wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause proble
On Wed, 9 Apr 2025 11:04:26 GMT, Kevin Walls wrote:
>> This is a long-standing oversight: HeapDumpPath does not recognise %p for
>> pid expansion.
>> The default filename uses a pid (e.g. java_pid1676937.hprof) but
>> HeapDumpPath does not.
>> It has always done a manual "root plus pid plus ext
On Thu, 10 Apr 2025 05:50:23 GMT, Serguei Spitsyn wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause pro
> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088), JVMTI
> `GetThreadGroupChildren` does an upcall to java. This results in
> a`ClassPrepare` event the first time it does this, and these events can cause
> problems (deadlocks) for the debugger or debug agent. The
> [JDK
On Thu, 10 Apr 2025 05:50:23 GMT, Serguei Spitsyn wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause pro
On Thu, 10 Apr 2025 09:16:56 GMT, Joel Sikström wrote:
>>> Note that any reference to pages from here on out refers to the concept of
>>> a heap region in ZGC, not pages in the operating system (OS), unless stated
>>> otherwise.
>>
>> # Background
>>
>> This PR addresses fragmentation by intr
As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088), JVMTI
`GetThreadGroupChildren` does an upcall to java. This results in
a`ClassPrepare` event the first time it does this, and these events can cause
problems (deadlocks) for the debugger or debug agent. The
[JDK-8352088](
On Wed, 9 Apr 2025 13:37:16 GMT, Joel Sikström wrote:
>> Note that any reference to pages from here on out refers to the concept of a
>> heap region in ZGC, not pages in the operating system (OS), unless stated
>> otherwise.
>
> # Background
>
> This PR addresses fragmentation by introducing
On Thu, 10 Apr 2025 08:44:28 GMT, Eirik Bjørsnøs wrote:
>> Justin Lu has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Replace InputStreamReader with BufferedReader
>
> FWIW, I checked out the revision of the commit previous to this change
Follow up to JDK-8319447 to change the VirtualThread implementation to use
FJP's delayed task handling.
The SPTE based implementation is not removed. It will continue to be used by
tests. If custom schedulers are exposed in the future then they will use this
implementation.
For timed-Object.wa
On Tue, 8 Apr 2025 14:11:21 GMT, Stefan Karlsson wrote:
>> Robert Toyonaga has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> exclude file mapping tests on AIX.
>
> test/hotspot/gtest/runtime/test_os.cpp line 1145:
>
>> 1143: EXPECT_TRUE
On Thu, 10 Apr 2025 17:59:15 GMT, Serguei Spitsyn wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause pro
Don't use includevirtualthreads=y unless the test requires it. Debuggers don't
usually use includevirtualthreads=y, so we should be doing most of our testing
without it. The only reason tests use it is because some tests need it so they
can find virtual threads in the debuggee by using vm.allThr
On Wed, 9 Apr 2025 21:26:15 GMT, Justin Lu wrote:
>> src/java.xml/share/classes/com/sun/org/apache/xml/internal/serializer/Encodings.properties
>> line 22:
>>
>>> 20: # Peter Smolik
>>> 21: Cp1250 WINDOWS-1250 0x00FF
>>> 22: # Patch attributed to hava...@underdusken.no (H�vard Wigtil)
>>
>> Th
On Wed, 9 Apr 2025 08:14:04 GMT, Serguei Spitsyn wrote:
> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088), JVMTI
> `GetThreadGroupChildren` does an upcall to java. This results in
> a`ClassPrepare` event the first time it does this, and these events can cause
> problems
On Thu, 10 Apr 2025 17:59:15 GMT, Serguei Spitsyn wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause pro
On Tue, 11 Feb 2025 15:56:39 GMT, Matthias Baesken wrote:
> The libjdwp is currently built with LOW optimization level, it could be built
> with SIZE optimization to lower the lib size by ~ 10 % on UNIX.
> On Windows LOW and SIZE currently translate to the same O1 optimization flag
> so no diff
> Don't use includevirtualthreads=y unless the test requires it. Debuggers
> don't usually use includevirtualthreads=y, so we should be doing most of our
> testing without it. The only reason tests use it is because some tests need
> it so they can find virtual threads in the debuggee by using v
On Tue, 8 Apr 2025 01:37:21 GMT, Chris Plummer wrote:
>> This is a long-standing oversight: HeapDumpPath does not recognise %p for
>> pid expansion.
>> The default filename uses a pid (e.g. java_pid1676937.hprof) but
>> HeapDumpPath does not.
>> It has always done a manual "root plus pid plus e
On Wed, 9 Apr 2025 08:14:04 GMT, Serguei Spitsyn wrote:
> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088), JVMTI
> `GetThreadGroupChildren` does an upcall to java. This results in
> a`ClassPrepare` event the first time it does this, and these events can cause
> problems
On Thu, 10 Apr 2025 20:31:13 GMT, Chris Plummer wrote:
>> Don't use includevirtualthreads=y unless the test requires it. Debuggers
>> don't usually use includevirtualthreads=y, so we should be doing most of our
>> testing without it. The only reason tests use it is because some tests need
>> i
On Thu, 10 Apr 2025 17:59:15 GMT, Serguei Spitsyn wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause pro
On Wed, 13 Sep 2023 17:38:28 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 l
On Tue, 11 Feb 2025 15:56:39 GMT, Matthias Baesken wrote:
> The libjdwp is currently built with LOW optimization level, it could be built
> with SIZE optimization to lower the lib size by ~ 10 % on UNIX.
> On Windows LOW and SIZE currently translate to the same O1 optimization flag
> so no diff
On Thu, 10 Apr 2025 17:59:15 GMT, Serguei Spitsyn wrote:
>> As noted in [JDK-8352088](https://bugs.openjdk.org/browse/JDK-8352088),
>> JVMTI `GetThreadGroupChildren` does an upcall to java. This results in
>> a`ClassPrepare` event the first time it does this, and these events can
>> cause pro
> Don't use includevirtualthreads=y unless the test requires it. Debuggers
> don't usually use includevirtualthreads=y, so we should be doing most of our
> testing without it. The only reason tests use it is because some tests need
> it so they can find virtual threads in the debuggee by using v
On Thu, 10 Apr 2025 21:32:05 GMT, Hendrik Schick wrote:
>> Chris Plummer has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Fix copyright.
>
> test/jdk/com/sun/jdi/RedefineNestmateAttr/TestNestmateAttr.java line 1:
>
>> 1: /*
>
> update c
41 matches
Mail list logo
