RFR: 8357086: os::xxx functions returning memory size should return size_t [v29]

[David Holmes]

On Wed, 20 Aug 2025 07:19:36 GMT, Anton Artemov <duke at openjdk.org> wrote:

>> Hi,
>> 
>> in this PR the output value types for functions which return memory are changed, namely:
>> 
>> 
>> static julong available_memory(); --> static bool available_memory(size_t& value);
>> static julong used_memory(); --> static bool used_memory(size_t& value);
>> static julong free_memory(); --> static bool free_memory(size_t& value); 
>> static jlong total_swap_space(); --> static bool total_swap_space(size_t& value);
>> static jlong free_swap_space(); --> static bool free_swap_space(size_t& value); 
>> static julong physical_memory(); --> static size_t physical_memory(size_t& value); 
>> 
>> 
>> The return boolean value, where available, indicates success, whereas the actual value is assigned to the input argument. The following recommended usage pattern is introduced: where applicable, an unsuccessful call is logged. 
>> 
>> `ATTRIBUTE_NODISCARD` macro is added as a placeholder for `[[nodiscard]]`, which will be available with C++17.
>> 
>> Tested in GHA and Tiers 1-5.
>
> Anton Artemov has updated the pull request incrementally with one additional commit since the last revision:
> 
>   8357086: Addressed reviewer's comments

src/hotspot/os/windows/os_windows.cpp line 869:

> 867:     return true;
> 868:   } else {
> 869:     assert(false, "GlobalMemoryStatusEx failed in win32::available_memory(): %u", ::GetLastError());

Suggestion:

    assert(false, "GlobalMemoryStatusEx failed in win32::available_memory(): %lu", ::GetLastError());

There is no consistency here but the primary ways we print `GetLastError` are using `%lu`, `%ld` or `%d`.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/25450#discussion_r2289632489