On Mon, 22 Apr 2024 16:24:06 GMT, Guoxiong Li wrote:
> Hi all,
>
> This patch removes the class `TenuredSpace` and adjusts its usages. After
> removing `TenuredSpace`, the file `space.inline.hpp` is empty, so I remove
> this file and change the included header file to `space.hpp`.
>
> The tes
On Fri, 19 Apr 2024 07:44:17 GMT, Richard Reingruber wrote:
>> An alternative for preemptively switching the W^X thread mode on macOS with
>> an AArch64 CPU. This implementation triggers the switch in response to the
>> SIGBUS signal if the *si_addr* belongs to the CodeCache area. With this
>>
On Fri, 19 Apr 2024 01:16:46 GMT, Alex Menkov wrote:
> The fix deprecates -XX:+UseNotificationThread VM option
>
> Testing: tier1-3,hs-tier5-svc
Looks good. Thank you for doing this.
-
Marked as reviewed by coleenp (Reviewer).
PR Review: https://git.openjdk.org/jdk/pull/18852#pu
WIP
This changeset contains hsdis for Windows/gcc Port. It supports both the
binutils and capstone backends, though the LLVM backend is left out due to
compatibility issues encountered during the build. Currently, which gcc
distributions are supported is still to be clarified, as several, rangi
On Tue, 23 Apr 2024 13:56:32 GMT, Julian Waters wrote:
> WIP
>
> This changeset contains hsdis for Windows/gcc Port. It supports both the
> binutils and capstone backends, though the LLVM backend is left out due to
> compatibility issues encountered during the build. Currently, which gcc
> di
On Tue, 23 Apr 2024 14:25:22 GMT, Magnus Ihse Bursie wrote:
> There's a huge amount of changes for just hsdis... You might have to separate
> out the infrastructure changes that seem to amount to most of the changes
> here.
>
> This is going to take me a while to get through.
Sorry, it's stil
On Wed, 17 Apr 2024 22:48:16 GMT, Dean Long wrote:
>> Before [JDK-8307190](https://bugs.openjdk.org/browse/JDK-8307190),
>> [JDK-8309673](https://bugs.openjdk.org/browse/JDK-8309673), and
>> [JDK-8301995](https://bugs.openjdk.org/browse/JDK-8301995), invokedynamic
>> operands needed to be rewr
On Wed, 17 Apr 2024 15:26:52 GMT, Matias Saavedra Silva
wrote:
> Before [JDK-8307190](https://bugs.openjdk.org/browse/JDK-8307190),
> [JDK-8309673](https://bugs.openjdk.org/browse/JDK-8309673), and
> [JDK-8301995](https://bugs.openjdk.org/browse/JDK-8301995), invokedynamic
> operands needed t
On Fri, 19 Apr 2024 07:44:17 GMT, Richard Reingruber wrote:
>> An alternative for preemptively switching the W^X thread mode on macOS with
>> an AArch64 CPU. This implementation triggers the switch in response to the
>> SIGBUS signal if the *si_addr* belongs to the CodeCache area. With this
>>
> Hi all,
>
> This patch removes the class `TenuredSpace` and adjusts its usages. After
> removing `TenuredSpace`, the file `space.inline.hpp` is empty, so I remove
> this file and change the included header file to `space.hpp`.
>
> The test `make test-tier1_gc` passed locally. Thanks for takin
> Hi all,
>
> This patch removes the class `TenuredSpace` and adjusts its usages. After
> removing `TenuredSpace`, the file `space.inline.hpp` is empty, so I remove
> this file and change the included header file to `space.hpp`.
>
> The test `make test-tier1_gc` passed locally. Thanks for takin
On Tue, 23 Apr 2024 17:22:41 GMT, Guoxiong Li wrote:
>> Hi all,
>>
>> This patch removes the class `TenuredSpace` and adjusts its usages. After
>> removing `TenuredSpace`, the file `space.inline.hpp` is empty, so I remove
>> this file and change the included header file to `space.hpp`.
>>
>>
On Thu, 18 Apr 2024 21:56:09 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
>>
On Wed, 17 Apr 2024 00:29:52 GMT, Serguei Spitsyn wrote:
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err`
> The fix deprecates -XX:+UseNotificationThread VM option
>
> Testing: tier1-3,hs-tier5-svc
Alex Menkov has updated the pull request with a new target base due to a merge
or a rebase. The pull request now contains two commits:
- Merge branch 'master' into deprecate_notif_thread
- fix
---
On Wed, 17 Apr 2024 00:29:52 GMT, Serguei Spitsyn wrote:
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err`
> Please review the updates to support a proposed new
> `-Xlint:dangling-doc-comments` option.
>
> The work can be thought of as in 3 parts:
>
> 1. An update to the `javac` internal class `DeferredLintHandler` so that it
> is possible to specify the appropriately configured `Lint` object when i
On Fri, 19 Apr 2024 01:16:46 GMT, Alex Menkov wrote:
> The fix deprecates -XX:+UseNotificationThread VM option
>
> Testing: tier1-3,hs-tier5-svc
This pull request has now been integrated.
Changeset: 25551662
Author:Alex Menkov
URL:
https://git.openjdk.org/jdk/commit/255516624723049
On Thu, 18 Apr 2024 21:56:09 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
>>
On Wed, 17 Apr 2024 00:29:52 GMT, Serguei Spitsyn wrote:
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err`
On Tue, 23 Apr 2024 20:47:34 GMT, Chris Plummer wrote:
>> Serguei Spitsyn has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> review: tweak in wait_for_state func to allow exp_state bit mask
>
> test/hotspot/jtreg/serviceability/jvmti/Object
On Wed, 17 Apr 2024 00:29:52 GMT, Serguei Spitsyn wrote:
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err`
On Tue, 23 Apr 2024 19:05:38 GMT, Patricio Chilano Mateo
wrote:
>> This is a simple fix of three similar asserts.
>> The `_target_jt->jvmti_vthread()` has to be used instead of
>> `_target_jt->vthread()`.
>> The `_target_jt->vthread()` can be outdated in some specific contexts as
>> shown in
On Wed, 17 Apr 2024 00:29:52 GMT, Serguei Spitsyn wrote:
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err`
> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
> event but has not released the `lockCheck` monitor yet. It has been fixed to
> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> same approach is used for `EnteringTask` threads. It has been
On Wed, 17 Apr 2024 00:29:52 GMT, Serguei Spitsyn wrote:
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err`
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err` stack trace.
>
> I've seen similar issue and already fixed
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err` stack trace.
>
> I've seen similar issue and already fixed
On Wed, 24 Apr 2024 00:01:45 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
>>
On Wed, 24 Apr 2024 02:49:56 GMT, Serguei Spitsyn wrote:
>> This is a simple fix of three similar asserts.
>> The `_target_jt->jvmti_vthread()` has to be used instead of
>> `_target_jt->vthread()`.
>> The `_target_jt->vthread()` can be outdated in some specific contexts as
>> shown in the `hs_
30 matches
Mail list logo
