On Sat, 15 Apr 2023 10:15:20 GMT, Kevin Walls wrote:
>> This test is failing often since 8304725 added a call to
>> Thread::current_in_asgct(). This can end up being called e.g. when
>> resolving calls, and then the OS last error value is lost.
>>
>> The test is reliable with a single warm-up
On Sat, 15 Apr 2023 10:15:20 GMT, Kevin Walls wrote:
>> This test is failing often since 8304725 added a call to
>> Thread::current_in_asgct(). This can end up being called e.g. when
>> resolving calls, and then the OS last error value is lost.
>>
>> The test is reliable with a single warm-up
On Wed, 12 Apr 2023 17:31:49 GMT, Roger Riggs wrote:
>> Define an internal jdk.internal.util.Architecture enumeration and static
>> methods to replace uses of the system property `os.arch`.
>> The enumeration values are defined to match those used in the build.
>> The initial values are: `X64, X
On Fri, 14 Apr 2023 19:23:05 GMT, Kevin Walls wrote:
> This test is failing often since 8304725 added a call to
> Thread::current_in_asgct(). This can end up being called e.g. when resolving
> calls, and then the OS last error value is lost.
>
> The test is reliable with a single warm-up call
> This test is failing often since 8304725 added a call to
> Thread::current_in_asgct(). This can end up being called e.g. when resolving
> calls, and then the OS last error value is lost.
>
> The test is reliable with a single warm-up call to getLastError.invoke()
> before the loop.
>
> The
