P4
This change replaces the internal use of `jlong` with `uint64_t` for
`Thread::_allocated_bytes`, and the related field
`ThreadService::_exited_allocated_bytes`.
The intent is to confine `jlong` usage to the JVM/Java boundary and avoid
propagating Java-specific types into deeper HotSpot runtime internals.
Since allocated byte counters are inherently non-negative,
`uint64_t` more accurately reflects the domain.
`Thread::_allocated_bytes`, and the related field
`ThreadService::_exited_allocated_bytes`.
The intent is to confine `jlong` usage to the JVM/Java boundary and avoid
propagating Java-specific types into deeper HotSpot runtime internals.
Since allocated byte counters are inherently non-negative,
`uint64_t` more accurately reflects the domain.
- links to
-
Commit(master)
openjdk/jdk/7ec561f8
-
Review(master)
openjdk/jdk/29792