RFR: 8351334: [ubsan] memoryReserver.cpp:552:60: runtime error: applying non-zero offset 1073741824 to null pointer [v5]

[Afshin Zafari]

On Wed, 17 Sep 2025 08:01:36 GMT, Axel Boldt-Christmas <aboldtch at openjdk.org> wrote:

> I think the use of `uint64_t` stems from the `UnscaledOopHeapMax` and `OopEncodingHeapMax` being typed as such. Unclear to me why they are not just `size_t`, as coops is a 64-bit VM feature.

Same to me. There are some/many cases of mixing type arithmetic like ` address + size_t < uint64_t`. It may not be any problem, but it'd been better if we can define a coding rule for these cases.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/26955#issuecomment-3306342645