https://gcc.gnu.org/g:b3ed4c006472b1ca29326dc3ce458412b76fc1c0
commit r17-1724-gb3ed4c006472b1ca29326dc3ce458412b76fc1c0 Author: Iain Sandoe <[email protected]> Date: Tue Jun 9 07:27:12 2026 +0100 aarch64: Use LLONG_MAX instead of LONG_LONG_MAX A recent change to aarch64-builtins.cc broke the build on Darwin. This is because it expects LONG_LONG_MAX to be defined. However, from the inclusion of limits.h, we can really only expect LLONG_MAX to be defined as per the descriptions for limits.h in the language standards. So this swaps LLONG_MAX for LONG_LONG_MAX. gcc/ChangeLog: * config/aarch64/aarch64-builtins.cc (aarch64_expand_prefetch_range_builtin): Use LLONG_MAX instead of LONG_LONG_MAX. Signed-off-by: Iain Sandoe <[email protected]> Diff: --- gcc/config/aarch64/aarch64-builtins.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config/aarch64/aarch64-builtins.cc b/gcc/config/aarch64/aarch64-builtins.cc index 4977c4abf348..f9bb6227e7e1 100644 --- a/gcc/config/aarch64/aarch64-builtins.cc +++ b/gcc/config/aarch64/aarch64-builtins.cc @@ -3794,7 +3794,7 @@ aarch64_expand_prefetch_range_builtin (tree exp, int fcode) non-negative integer. However it is meaningless for values less than 2^15 or greater than 2^29. */ uint64_t reuse_distance = require_const_argument (exp, argno++, 0, - LONG_LONG_MAX); + LLONG_MAX); if (seen_error ()) return;
