44d469c5f8
This commit adds a separate Fortran compiler identification mechanism to the testsuite, similar to the existing one for C/C++. Before this change, the options and version for the Fortran compiler specified when running the testsuite with F90_FOR_TARGET set, was detected via its respective C compiler. So running the testsuite as make check TEST=gdb.fortran/*.exp CC_FOR_TARGET=gcc F90_FOR_TARGET=ifx or even make check TEST=gdb.fortran/*.exp F90_FOR_TARGET=ifx would use the gcc compiler inside the procedures get_compiler_info and test_compiler_info to identify compiler flags and the compiler version. This could sometimes lead to unpredictable outputs. It also limited testsuite execution to combinations where C and Fortran compiler would come from the same family of compiers (gcc/gfortran, icc/ifort, icx/ifx, clang/flang ..). This commit enables GDB to detect C and Fortran compilers independently of each other. As most/nearly all Fortran compilers have a mechanism for preprocessing files in a C like fashion we added the exact same meachnism that already existed for C/CXX. We let GDB preprocess a file with the compilers Fortran preprocessor and evaluate the preprocessor defined macros in that file. This enables GDB to properly run heterogeneous combinations of C and Fortran compilers such as CC_FOR_TARGET='gcc' and F90_FOR_TARGET='ifort' or enables one to run the testsuite without specifying a C compiler as in make check TESTS=gdb.fortran/*.exp F90_FOR_TARGET='ifx' make check TESTS=gdb.fortran/*.exp F90_FOR_TARGET='flang' On the other hand this also requires one to always specify a identification mechanism for Fortran compilers in the compiler.F90 file. We added identification for GFORTRAN, FLANG (CLASSIC and LLVM) IFX, IFORT, and ARMFLANG for now. Classic and LLVM flang were each tested with their latest releases on their respective release pages. Both get recognized by the new compiler identification and we introduced the two names flang-classic and flang-llvm to distinguish the two. While LLVM flang is not quite mature enough yet for running the testsuite we still thought it would be a good idea to include it already. For this we added a case for the fortran_main procedure. LLVM flang uses 'MAIN__' as opposed to classic flang which uses 'MAIN_' here. We did not have the possibility to test ARMFLANG - the versioning scheme here was extracted from its latest online documentation. We changed the test_compiler_info procedure to take another optional argument, the language string, which will be passed though to the get_compiler_info procedure. Passing 'f90' or 'c++' here will then trigger the C++/Fortran compiler identification within get_compiler_info. The latter procedure was extended to also handle the 'f90' argument (similarly to the already existing 'c++' one). Co-authored-by: Nils-Christian Kempke <nils-christian.kempke@intel.com>
69 lines
2.6 KiB
Fortran
69 lines
2.6 KiB
Fortran
/* Copyright 2022 Free Software Foundation, Inc.
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
it under the terms of the GNU General Public License as published by
|
|
the Free Software Foundation; either version 2 of the License, or
|
|
(at your option) any later version.
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
GNU General Public License for more details.
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>. */
|
|
|
|
set compiler_info "unknown"
|
|
|
|
#if defined (__GFORTRAN__)
|
|
set compiler_info [join {gfortran __GNUC__ __GNUC_MINOR__ __GNUC_PATCHLEVEL__} -]
|
|
#endif
|
|
|
|
/* ARM seems to not define a patch version. */
|
|
#if defined (__ARM_LINUX_COMPILER__)
|
|
set compiler_info [join {armflang __armclang_major__ __armclang_minor__ 0} -]
|
|
#endif
|
|
|
|
/* Classic flang and LLVM flang emit their respective macros differently. */
|
|
|
|
/* LLVM flang complains about non Fortran tokens so we do not use "{" here. */
|
|
#if defined (__flang__)
|
|
set major __flang_major__
|
|
set minor __flang_minor__
|
|
set patch __flang_patchlevel__
|
|
set compiler_info [join "flang-llvm $major $minor $patch" -]
|
|
#endif
|
|
|
|
/* Classic Flang. */
|
|
#if defined (__FLANG)
|
|
set compiler_info [join {flang-classic __FLANG_MAJOR__ __FLANG_MINOR__ __FLANG_PATCHLEVEL__} -]
|
|
#endif
|
|
|
|
/* Intel LLVM emits a string like 20220100 with version 2021.2.0 and higher. */
|
|
#if defined (__INTEL_LLVM_COMPILER)
|
|
set major [string range __INTEL_LLVM_COMPILER 0 3]
|
|
set minor [string range __INTEL_LLVM_COMPILER 4 5]
|
|
set patch [string range __INTEL_LLVM_COMPILER 6 7]
|
|
set compiler_info [join "ifx $major $minor $patch" -]
|
|
#elif defined (__INTEL_COMPILER)
|
|
/* Starting with 2021 the ifort versioning scheme changed. Before, Intel ifort
|
|
would define its version as e.g. 19.0.0 or rather __INTEL_COMPILER would be
|
|
emitted as 1900. With 2021 the versioning became e.g. 2021.1 defined in
|
|
__INTEL_COMPILER.__INTEL_COMPILER_UPDATE. No patch is emitted since the
|
|
change. This compiler identification might not work with ifort versions
|
|
smaller than 10. */
|
|
#if (__INTEL_COMPILER < 2021)
|
|
set major [string range __INTEL_COMPILER 0 1]
|
|
set minor [string range __INTEL_COMPILER 2 2]
|
|
#if defined (__INTEL_COMPILER_UPDATE)
|
|
set patch __INTEL_COMPILER_UPDATE
|
|
#else
|
|
set patch [string range __INTEL_COMPILER 3 3]
|
|
#endif
|
|
#else
|
|
set major __INTEL_COMPILER
|
|
set minor __INTEL_COMPILER_UPDATE
|
|
set patch 0
|
|
#endif
|
|
set compiler_info [join "ifort $major $minor $patch" -]
|
|
#endif
|