owing section as a comment in
> the source code
>
> ## Fast Locking
>
> CAS on locking bits in markWord.
> 0b00 (Fast Locked) <--> 0b01 (Unlocked)
>
> When locking and 0b00 (Fast Locked) is observed, it may be beneficial to
> avoid inflating by spinning
On Mon, 8 Jul 2024 10:58:29 GMT, Thomas Wuerthinger wrote:
> OK. Will there be a CSR or JEP for this?
There is no plan for this, nor should it be required. It’s an internal
implementation.
> When do you approximately expect this to land in main line?
ASAP. Compatibility for the field name
On Mon, 8 Jul 2024 09:39:32 GMT, Thomas Wuerthinger wrote:
> Is this change expected to require JVMCI and/or Graal JIT changes?
Support for `UseObjectMonitorTable` would require changes to Graal JIT.
(`UseObjectMonitorTable` is off by default).
Minimal support would be to call into the VM for
When inflating a monitor the `ObjectMonitor*` is written directly over the
`markWord` and any overwritten data is displaced into a displaced `markWord`.
This is problematic for concurrent GCs which needs extra care or looser
semantics to use this displaced data. In Lilliput this data also
On Mon, 20 May 2024 06:41:45 GMT, Axel Boldt-Christmas
wrote:
> Improve `java/util/zip/EntryCount64k.java` stderr parsing by ignoring
> deprecated warnings. Testing non-generational ZGC requires the use of a
> deprecated option.
This pull request has now been integrated.
Changeset:
On Mon, 20 May 2024 07:27:19 GMT, Axel Boldt-Christmas
wrote:
>> Improve `java/util/zip/EntryCount64k.java` stderr parsing by ignoring
>> deprecated warnings. Testing non-generational ZGC requires the use of a
>> deprecated option.
>
> Axel Boldt-Christmas has
On Mon, 20 May 2024 06:42:19 GMT, Axel Boldt-Christmas
wrote:
> Improve ` java/util/logging/LoggingDeadlock2.java` stderr parsing by ignoring
> deprecated warnings. Testing non-generational ZGC requires the use of a
> deprecated option.
This pull request has now been integrated.
On Mon, 20 May 2024 07:25:12 GMT, Axel Boldt-Christmas
wrote:
>> Improve ` java/util/logging/LoggingDeadlock2.java` stderr parsing by
>> ignoring deprecated warnings. Testing non-generational ZGC requires the use
>> of a deprecated option.
>
> Axel Boldt-Christmas has
On Mon, 20 May 2024 10:11:26 GMT, David Holmes wrote:
>> Axel Boldt-Christmas has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Update copyright year
>
> test/lib/jdk/test/lib/process/OutputAna
> Improve `java/util/zip/EntryCount64k.java` stderr parsing by ignoring
> deprecated warnings. Testing non-generational ZGC requires the use of a
> deprecated option.
Axel Boldt-Christmas has updated the pull request incrementally with one
additional commit since the last revision:
> Improve ` java/util/logging/LoggingDeadlock2.java` stderr parsing by ignoring
> deprecated warnings. Testing non-generational ZGC requires the use of a
> deprecated option.
Axel Boldt-Christmas has updated the pull request incrementally with one
additional commit since the last
Improve ` java/util/logging/LoggingDeadlock2.java` stderr parsing by ignoring
deprecated warnings. Testing non-generational ZGC requires the use of a
deprecated option.
-
Commit messages:
- 8332495: java/util/logging/LoggingDeadlock2.java fails with AssertionError:
Some tests
Improve `java/util/zip/EntryCount64k.java` stderr parsing by ignoring
deprecated warnings. Testing non-generational ZGC requires the use of a
deprecated option.
-
Commit messages:
- 8332494: java/util/zip/EntryCount64k.java failing with
java.lang.RuntimeException: '\\A\\Z'
On Fri, 27 Oct 2023 09:48:00 GMT, Leo Korinth wrote:
> Update method name after huge renaming conflict
Marked as reviewed by aboldtch (Reviewer).
Trivial fix.
-
PR Review: https://git.openjdk.org/jdk/pull/16395#pullrequestreview-1701406738
PR Comment:
On Tue, 20 Jun 2023 11:17:40 GMT, Axel Boldt-Christmas
wrote:
> Hi all,
>
> This pull request contains a backport of commit
> [a0595761](https://github.com/openjdk/jdk/commit/a0595761ef35c4eec8cb84326a869b9473cd5bba)
> from the [openjdk/jdk](https://git.openjdk.org/
Hi all,
This pull request contains a backport of commit
[a0595761](https://github.com/openjdk/jdk/commit/a0595761ef35c4eec8cb84326a869b9473cd5bba)
from the [openjdk/jdk](https://git.openjdk.org/jdk) repository.
The commit being backported was authored by Axel Boldt-Christmas on 20 Jun 2023
On Fri, 16 Jun 2023 09:14:10 GMT, Axel Boldt-Christmas
wrote:
> The current implementation for testing generational ZGC with jtreg is
> implemented with a filter on the mode flag `ZGenerational`. Because of this
> only environments which set this flag explicitly will run most of
On Mon, 19 Jun 2023 06:55:52 GMT, Axel Boldt-Christmas
wrote:
>> The current implementation for testing generational ZGC with jtreg is
>> implemented with a filter on the mode flag `ZGenerational`. Because of this
>> only environments which set this flag explicitly will run
On Mon, 19 Jun 2023 09:04:17 GMT, Thomas Stuefe wrote:
> How much time do we spend now in GHAs on the additional Zgenerational tests?
> In any case, this makes sense.
This adds around 40 more tests per platform. The runtime of GHA seems to have a
lot of run to run variance. Most new tests are
On Fri, 16 Jun 2023 20:31:28 GMT, Daniel D. Daugherty
wrote:
> Hmmm... hopefully `vm.gc.ZSingelgen` is really `vm.gc.ZSinglegen`. If so you
> might want to fix the PR description.
What part are you worried about? When would `vm.gc.ZSingelgen` be invalid?
Also what part of the PR requires
On Sat, 17 Jun 2023 13:24:24 GMT, Alan Bateman wrote:
>> Axel Boldt-Christmas has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix wrong ZGenerational flag in VectorRebracket128Test.java
>
> test/jdk/j
ith a different
> max heap size for ZGenerational, but it is not the intent to dispatch the
> test to both G1 and generational ZGC if Generational ZGC is not specified.
>
> `test/jdk/java/lang/management/MemoryMXBean/MemoryTest.java` was also changed
> to not filter but instead disp
ith a different
> max heap size for ZGenerational, but it is not the intent to dispatch the
> test to both G1 and generational ZGC if Generational ZGC is not specified.
>
> `test/jdk/java/lang/management/MemoryMXBean/MemoryTest.java` was also changed
> to not filter but instead disp
The current implementation for testing generational ZGC with jtreg is
implemented with a filter on the mode flag `ZGenerational`. Because of this
only environments which set this flag explicitly will run most of the tests.
So they get missed in Github Actions and for developers running jtreg
24 matches
Mail list logo
