On Tue, 17 Nov 2026 11:52:49 GMT, Matthias Baesken <[email protected]> wrote:

> > SAFE_TO_ALLOC checks an unsigned 32-bit bound, so it can accept a 
> > mathematical product above INT_MAX.
> 
> Should we maybe have another macro that does a different check?

Good point. A separate check against INT_MAX would make sense where the result 
is stored in an int. I'd prefer to keep the existing SAFE_TO_ALLOC semantics 
unchanged, since not all callers require a signed integer bound.

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

PR Comment: https://git.openjdk.org/jdk/pull/33915#issuecomment-6969839004

Reply via email to