RFR: 8346916: [REDO] align_up has potential overflow [v2]

[Casper Norrbin]

On Thu, 27 Feb 2025 10:24:31 GMT, Casper Norrbin <cnorrbin at openjdk.org> wrote:

>> Hi everyone,
>> 
>> The `align_up` function can potentially overflow, resulting in undefined behavior. Most use cases rely on the assumption that aligned_result >= original. To address this, I've added an assertion to verify this condition.
>> 
>> The original PR (#20808) missed cases where overflow checks already existed, so I've now went through usages of `align_up` and found the places with explicit checks. Most notably, #23168 added `align_up_or_null` to metaspace, but this function is also useful elsewhere. Given this, I relocated it to `align.hpp`, alongside the rest of the alignment functions.
>> 
>> Additionally, I've created `align_up_or_min`, which behaves similarly to the original align_up but handles overflows predictably across all integer types. This new function is used in the locations where overflow checks already exist, providing a safer alternative.
>
> Casper Norrbin has updated the pull request incrementally with one additional commit since the last revision:
> 
>   reverted gcarguments and updated test

I have reverted `gcArguments.cpp` so that it now asserts on alignment. For this, a line was added to `TestOptionsWithRanges` to stop `-XX:MinHeapDeltaBytes` from being tested with int_max, since that would overflow and crash.

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

PR Comment: https://git.openjdk.org/jdk/pull/23711#issuecomment-2687539063