[PATCH] aarch64: Use __LONG_LONG_MAX__ instead of LONG_LONG_MAX

[Iain Sandoe]

Builds completed on aarch64 linux and (with devt patches) darwin,
thoughts?  Maybe LLONG_MAX is sufficiently portable?
or  OK for trunk?
thanks
Iain

--- 8< ---

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
(this seems to be the spelling mentioned in the std documents).  However,
we can resonably expect the compiler's __LONG_LONG_MAX__ to be available.

So this swaps __LONG_LONG_MAX__ for LONG_LONG_MAX.

gcc/ChangeLog:

        * config/aarch64/aarch64-builtins.cc
        (aarch64_expand_prefetch_range_builtin): Use __LONG_LONG_MAX__
        instead of LONG_LONG_MAX.

Signed-off-by: Iain Sandoe <i...@sandoe.co.uk>
---
 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 4977c4abf34..5acbd850522 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);
+                                                         __LONG_LONG_MAX__);
 
        if (seen_error ())
          return;
-- 
2.50.1 (Apple Git-155)