summaryrefslogtreecommitdiffstats
path: root/Modules/CMakeFortranCompilerId.F.in
diff options
context:
space:
mode:
authorJustin LaPolla <jlapolla@cray.com>2020-12-01 16:42:06 (GMT)
committerBrad King <brad.king@kitware.com>2020-12-01 17:20:47 (GMT)
commit9ee4a42813b10e541e17bc3b4e50dfd99f9dab14 (patch)
tree9532f43c1be602cbb0a46d8e41c1b834190c6656 /Modules/CMakeFortranCompilerId.F.in
parentf264f1d783d57c70a0864768b6b1aa44fc94194a (diff)
downloadCMake-9ee4a42813b10e541e17bc3b4e50dfd99f9dab14.zip
CMake-9ee4a42813b10e541e17bc3b4e50dfd99f9dab14.tar.gz
CMake-9ee4a42813b10e541e17bc3b4e50dfd99f9dab14.tar.bz2
Cray: Fix Cray compiler detection on new platforms
Customer reported problems detecting the Cray compiler on their Apollo80 system. We were checking for the __CRAYXC and __CRAYXE predefined macros. These macros reflect the platform that the compiler is running on, i.e. Cray XC and Cray XE machines. Naturally, this didn't work on Apollo80. This commit uses the official Cray compiler identification macros which are defined on every platform: CCE Version C Macro C++ Macro Fortran Macro ============ ======== ========= ============= version < 9 _CRAYC _CRAYC _CRAYFTN version >= 9 __cray__ __cray__ _CRAYFTN
Diffstat (limited to 'Modules/CMakeFortranCompilerId.F.in')
-rw-r--r--Modules/CMakeFortranCompilerId.F.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/Modules/CMakeFortranCompilerId.F.in b/Modules/CMakeFortranCompilerId.F.in
index 30f8d4c..7e8828b 100644
--- a/Modules/CMakeFortranCompilerId.F.in
+++ b/Modules/CMakeFortranCompilerId.F.in
@@ -108,7 +108,7 @@
#else
PRINT *, 'INFO:compiler[]'
#endif
-#if defined(__CRAYXE) || defined(__CRAYXC)
+#if defined(_CRAYFTN)
PRINT *, 'INFO:compiler_wrapper[CrayPrgEnv]'
#endif