On Wed, 4 Dec 2024 05:53:22 GMT, Tom Rodriguez wrote:
>> The notification that finalize is complete should be done after printing the
>> message because in Xcomp mode there might be a significant delay at the
>> println so the object hasn't actually been finalized yet.
>
> Tom Rodriguez has upd
> The notification that finalize is complete should be done after printing the
> message because in Xcomp mode there might be a significant delay at the
> println so the object hasn't actually been finalized yet.
Tom Rodriguez has updated the pull request with a new target base due to a
merge o
On Tue, 29 Oct 2024 16:52:45 GMT, Tom Rodriguez wrote:
> The notification that finalize is complete should be done after printing the
> message because in Xcomp mode there might be a significant delay at the
> println so the object hasn't actually been finalized yet.
It probably should be vola
On Tue, 29 Oct 2024 16:52:45 GMT, Tom Rodriguez wrote:
> The notification that finalize is complete should be done after printing the
> message because in Xcomp mode there might be a significant delay at the
> println so the object hasn't actually been finalized yet.
Would it help for `Basic.f
On Tue, 29 Oct 2024 16:52:45 GMT, Tom Rodriguez wrote:
> The notification that finalize is complete should be done after printing the
> message because in Xcomp mode there might be a significant delay at the
> println so the object hasn't actually been finalized yet.
LGTM
-
Marke
The notification that finalize is complete should be done after printing the
message because in Xcomp mode there might be a significant delay at the println
so the object hasn't actually been finalized yet.
-
Commit messages:
- 8343213: TEST_BUG: [Graal] java/lang/ref/Basic.java fa
