On Mon, 20 Mar 2023 19:47:10 GMT, Eirik Bjorsnos wrote:
> Please review this PR which replaces the use of outdated JVM flags for
> setting up debugging in the test value004.java
>
> This is part of an ongoing effort to remove use of the outdated flag
> '-Djava.compiler" such that the option it
On Mon, 20 Mar 2023 20:53:41 GMT, Eirik Bjorsnos wrote:
> Please review this PR which removes the following outdated guard/check from
> SunCommandLineLauncher:
>
>
> if ((options.indexOf("-Djava.compiler=") != -1) &&
> (options.toLowerCase().indexOf("-djava.compiler=none") == -1)) {
>
On Tue, 21 Mar 2023 02:49:15 GMT, Chris Plummer wrote:
> Please make sure you run the jdk/com/sun/jdi tests and the jdb, jdwp, and jdi
> test under hotspot/jtreg/vmTestbase/nsk
Tests passed:
==
Test summary
==
TEST
On Tue, 24 Jan 2023 21:10:31 GMT, Johan Sjölen wrote:
>> Hi, this PR changes all occurrences of NULL to nullptr for the subdirectory
>> share/jfr/. Unfortunately the script that does the change isn't perfect, and
>> so we
>> need to comb through these manually to make sure nothing has gone wron
On Mon, 20 Mar 2023 14:29:35 GMT, Matias Saavedra Silva
wrote:
>> The current structure used to store the resolution information for
>> invokedynamic, ConstantPoolCacheEntry, is difficult to interpret due to its
>> ambigious fields f1 and f2. This structure can hold information for fields,
>>
Hi Volker.
JEP 261 states: "The dynamic loading of JVM TI agents will be disabled by
default in a future release. To prepare for that change we recommend that
applications that allow dynamic agents start using the option
-XX:+EnableDynamicAgentLoading to enable that loading explicitly." The pur
On Tue, 21 Mar 2023 10:51:08 GMT, Andrew Haley wrote:
>> Matias Saavedra Silva has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix riscv interpreter mistake and acquire semantics
>
> src/hotspot/cpu/aarch64/templateTable_aarch64.cpp line
On Tue, 21 Mar 2023 10:49:32 GMT, Andrew Haley wrote:
>> Matias Saavedra Silva has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix riscv interpreter mistake and acquire semantics
>
> src/hotspot/cpu/aarch64/templateTable_aarch64.cpp line
On Thu, 16 Mar 2023 21:02:09 GMT, Chris Plummer wrote:
> The debuggee main method creates two threads and then starts them:
>
>
> public static void main(String[] args) {
> System.out.println("Howdy!");
> Thread t1 = TestScaffold.newThread(new InvokeHangTarg(), name1);
>
> The current structure used to store the resolution information for
> invokedynamic, ConstantPoolCacheEntry, is difficult to interpret due to its
> ambigious fields f1 and f2. This structure can hold information for fields,
> methods, and invokedynamics and each of its fields can hold different
> Summaries:
> 1. A few recommendations about updating the constant API is made at
> https://mail.openjdk.org/pipermail/classfile-api-dev/2023-March/000233.html
> and I may update this patch shall the API changes be integrated before
> 2. One ASM library-specific test, `LambdaAsm` is removed. Oth
There are two GC related issues with this test that are being addressed. The
test was limiting the heap size to 6m so if there is still a leak, it will be
detected quickly. This proved to be too small of a size when using ZGC. For the
most part changing the size to 7m fixed this issue. However,
On Tue, 21 Mar 2023 17:40:46 GMT, Richard Reingruber wrote:
>> src/hotspot/cpu/aarch64/templateTable_aarch64.cpp line 2337:
>>
>>> 2335: // Load-acquire the adapter method
>>> 2336: __ lea(method, Address(cache,
>>> in_bytes(ResolvedIndyEntry::method_offset(;
>>> 2337: __ ldar(method,
> There are two GC related issues with this test that are being addressed. The
> test was limiting the heap size to 6m so if there is still a leak, it will be
> detected quickly. This proved to be too small of a size when using ZGC. For
> the most part changing the size to 7m fixed this issue. H
On Thu, 16 Mar 2023 20:56:15 GMT, Roman Kennke wrote:
>> This change adds a fast-locking scheme as an alternative to the current
>> stack-locking implementation. It retains the advantages of stack-locking
>> (namely fast locking in uncontended code-paths), while avoiding the overload
>> of the
The fix is to enable support for late binding JVMTI agents.
The fix includes:
- New function `JvmtiEnvBase::enable_virtual_threads_notify_jvmti()` which does
enabling JVMTI VTMS transition notifications in case of agent loaded into
running VM. This function executes a VM operation counting VTMS t
> The fix is to enable support for late binding JVMTI agents.
> The fix includes:
> - New function `JvmtiEnvBase::enable_virtual_threads_notify_jvmti()` which
> does enabling JVMTI VTMS transition notifications in case of agent loaded
> into running VM. This function executes a VM operation count
> The fix is to enable support for late binding JVMTI agents.
> The fix includes:
> - New function `JvmtiEnvBase::enable_virtual_threads_notify_jvmti()` which
> does enabling JVMTI VTMS transition notifications in case of agent loaded
> into running VM. This function executes a VM operation count
18 matches
Mail list logo
