[lmi-commits] [lmi] master 05fe1207 2/5: Use LMI_CLANG rather than __clang__ for consistency

[Greg Chicares]

branch: master
commit 05fe120792ae6f326f1791e201277135ebdcc557
Author: Vadim Zeitlin <vadim@tt-solutions.com>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Use LMI_CLANG rather than __clang__ for consistency
    
    No real changes, just consistently use LMI-specific symbols for compiler
    identification, as it is already done for MSVC just below.
---
 fdlibm.hpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fdlibm.hpp b/fdlibm.hpp
index 4c99b1da..3ddfb220 100644
--- a/fdlibm.hpp
+++ b/fdlibm.hpp
@@ -45,11 +45,11 @@
 
 // Apparently the clang maintainers believe that floating-point
 // endianness is necessarily the same as integer endianness.
-#if defined __clang__
+#if defined LMI_CLANG
 #   if !defined __FLOAT_WORD_ORDER__ && defined __BYTE_ORDER__
 #       define __FLOAT_WORD_ORDER__ __BYTE_ORDER__
 #   endif // !defined __FLOAT_WORD_ORDER__ && defined __BYTE_ORDER__
-#endif // defined __clang__
+#endif // defined LMI_CLANG
 
 // And MSVC maintainers don't believe in having different endianness
 // values at all, so the compiler never predefines these symbols.