summaryrefslogtreecommitdiffstats
path: root/Modules/Compiler
Commit message (Collapse)AuthorAgeFilesLines
* LLVMFlang-Fortran: Add flags for build typesTarun Prabhu2023-08-191-0/+4
| | | | Fixes: #25193
* Clang: use -std=c23 for Clang 18+Raul Tambre2023-08-151-1/+4
| | | | Canonical flag changed in LLVM commit 13629b140801870feff855ca168edf6b34dbef8d.
* Merge topic 'armclang-update-version-computation' into release-3.27Brad King2023-07-181-1/+1
|\ | | | | | | | | | | | | 65fac2fa35 ARMClang: Fix computation of compiler semantic version patch level Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8636
| * ARMClang: Fix computation of compiler semantic version patch levelDaniel Brondani2023-07-181-1/+1
| | | | | | | | | | | | According to ARMClang documentation 6.20, the patch version number should not include the last two digits of `__ARMCOMPILER_VERSION`, which are reserved for internal use by ARM.
* | Merge topic 'support_nvhpc_versions_without_isystem' into release-3.27Brad King2023-06-261-0/+4
|\ \ | | | | | | | | | | | | | | | | | | | | | f73ae7c510 NVHPC: Support nvfortran versions that don't support isystem Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !8588
| * | NVHPC: Support nvfortran versions that don't support isystemRobert Maynard2023-06-231-0/+4
| | | | | | | | | | | | Fixes: #25019
* | | link dependencies: deactivate the featureMarc Chevrier2023-06-231-3/+10
|/ / | | | | | | | | | | | | Unfortunately it breaks in combination with LTO due to a bug in the GNU linker. Fixes: #25014
* | Link Step: ensure the correct linker is used for depfile configurationMarc Chevrier2023-05-282-10/+3
| | | | | | | | This is related to MR !8443.
* | Merge topic 'clang_cxx26'Brad King2023-05-181-0/+2
|\ \ | | | | | | | | | | | | | | | | | | 0183956d30 Clang: C++26 support Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8480
| * | Clang: C++26 supportRaul Tambre2023-05-161-0/+2
| | | | | | | | | | | | | | | Added in LLVM commit b763d6a4ed4650c74c6846d743156468563b0e31. This time the final flag form is supported from the get-go to reduce churn.
* | | IAR: Added support for IAR C/C++ Compiler for Microchip AVR 8.10+Felipe Torrezan2023-05-162-2/+2
| | | | | | | | | | | | | | | | | | - Added C17 support - Added C++17 support - Changed: IAR UBROF Linker (XLINK) suffixed with target architecture (xlinkavr)
* | | Merge topic 'iar-align-output-extension'Brad King2023-05-163-2/+8
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | cfec4c1c5e IAR: Enforce output extension for xlink targets 7fec8f993b IAR: Replace extension for compiler and assembler Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8477
| * | IAR: Enforce output extension for xlink targetsJoakim Lönnberg2023-05-122-2/+7
| | |
| * | IAR: Replace extension for compiler and assemblerJoakim Lönnberg2023-05-081-0/+1
| | |
* | | Merge topic 'dankm/tcsuffix'Brad King2023-05-102-0/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6a82852dc2 Allow toolchain suffix without leading dash Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Reviewed-by: Ben Boeckel <ben.boeckel@kitware.com> Merge-request: !8462
| * | | Allow toolchain suffix without leading dashDan McGregor2023-05-092-0/+5
| |/ / | | | | | | | | | | | | | | | | | | | | | FreeBSD installs both LLVM and gcc with tools named after the major version, in the form "clang<major>", such as "clang16". Detect compilers named this way, and find the related toolchain tools.
* | | Clang: use -std=c++23 for Clang 17.0+Raul Tambre2023-05-081-1/+4
|/ / | | | | | | Canonical flag changed in LLVM commit ba15d186e5cef2620d562c6c9d9a6d570382cd0a.
* | Link step: use linker dependency linker fileMarc Chevrier2023-05-032-0/+47
| | | | | | | | | | | | Based on work done by @ben.boeckel (!8051) Fixes: #22217
* | Merge topic 'iar-silent-flag'Brad King2023-04-281-3/+7
|\ \ | | | | | | | | | | | | | | | | | | 01e944128d IAR: Move linker silencing flag to CMAKE_EXE_LINKER_FLAGS Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8421
| * | IAR: Move linker silencing flag to CMAKE_EXE_LINKER_FLAGSFelipe Torrezan2023-04-261-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | The IAR linker silencer flag was previously hardcoded in `CMAKE_${lang}_LINKER_EXECUTABLE`. Move the flag to a place that is under the end user's control. The default behavior (silenced linker) is not changed. Fixes: #24828
* | | Ninja: Revert "Exclude NVHPC -Werror flags during Fortran preprocessing"Brad King2023-04-261-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | Revert commit 6b58cdd4cf (Ninja: Exclude NVHPC -Werror flags during Fortran preprocessing, 2023-04-04). Since commit 9d40f01442 (NVHPC: Use -Werror for COMPILE_OPTIONS_WARNING_AS_ERROR, 2023-04-13), `nvfortran` can handle the plain `-Werror` flag during preprocessing. Issue: #24665
* | | NVHPC: Use -Werror for COMPILE_OPTIONS_WARNING_AS_ERRORRobert Maynard2023-04-252-2/+2
|/ / | | | | | | | | | | | | | | | | | | | | | | The previously-used `-Werror all-warnings` is not supported by the NVHPC suite of compilers. This previously worked since `-Werror` was being used and `all-warnings` was being excluded. We thought this was the correct syntax due to incorrect documentation about `-Werror`, which stated the argument should be space-separated, while it should actually be separated with `=` or `,`. Issue: #24665
* | Ninja: Exclude NVHPC -Werror flags during Fortran preprocessingBrad King2023-04-041-0/+1
| | | | | | | | | | | | | | | | The Ninja generator preprocesses Fortran separately in order to scan for module dependencies. NVHPC's `nvfortran` does not support its `-Werror` flag while preprocessing with `-E`, so filter it out. Fixes: #24665
* | IBMClang: No thin LTO on AIXNicole Rabjohn2023-03-231-1/+4
| | | | | | | | AIX does not yet support thin LTO.
* | Merge topic 'clang-windows-cxx-modules'Brad King2023-03-211-13/+15
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | 1b7c26da49 Ninja: Wrap rules using '>' shell redirection with 'cmd /C' on Windows ffd8537acf Clang: Record Clang 16.0 C++ modules flags only for GNU-like front-end 6013227230 cmGlobalNinjaGenerator: Use forward slashes in clang modmap format on Windows d9d74b5e8a cmDyndepCollation: Drop outdated mentions of CXX_MODULE_INTERNAL_PARTITIONS edab56d29a cmLocalNinjaGenerator: De-duplicate condition for using 'cmd /C' on Windows 8ebe3f92b3 cmGlobalNinjaGenerator: Detect GNU-like command-line for dyndep collator f3ca199c9b cmGlobalNinjaGenerator: Factor out GNU-like command-line detection on Windows f79817fcf0 cmCxxModuleMapper: Use value semantics in path conversion callback ... Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8346
| * Clang: Record Clang 16.0 C++ modules flags only for GNU-like front-endBrad King2023-03-201-13/+15
| | | | | | | | | | | | | | | | | | | | | | The settings added by commit 3fe8e33f27 (Clang: Record Clang 16.0 flags for our experimental C++ modules support, 2023-03-03, v3.26.0-rc6~6^2) work only for the GNU-like `clang++` front-end, and not for the MSVC-like `clang-cl` on Windows. Also quote the path to `clang-scan-deps` to support spaces in its path. Issue: #24611
* | IAR: Version update for arm assemblerJoakim Lönnberg2023-03-161-1/+1
| |
* | Merge topic 'iar-improve-asm'Brad King2023-03-152-27/+63
|\ \ | | | | | | | | | | | | | | | | | | 21f19d6af7 IAR:Improved assembler support Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8323
| * | IAR:Improved assembler supportJoakim Lönnberg2023-03-142-27/+63
| | |
* | | Merge topic 'support_cubin_fatbin_optix_cuda_output'Brad King2023-03-141-0/+5
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 2def6a874b CUDA: Add support for CUBIN, FATBIN, and OPTIXIR compilation Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !8259
| * | CUDA: Add support for CUBIN, FATBIN, and OPTIXIR compilationRobert Maynard2023-03-131-0/+5
| | |
* | | Merge topic 'clang-16-cxx-modules'Brad King2023-03-061-0/+14
|\ \ \ | |/ / |/| / | |/ | | | | | | | | | | 3fe8e33f27 Clang: Record Clang 16.0 flags for our experimental C++ modules support Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: scivision <michael@scivision.dev> Acked-by: Alex <leha-bot@yandex.ru> Merge-request: !8285
| * Clang: Record Clang 16.0 flags for our experimental C++ modules supportBrad King2023-03-031-0/+14
| | | | | | | | LLVM/Clang 16.0 now contains official support for what CMake needs.
* | IAR: Tolerate variables named for languagesJoakim Lönnberg2023-02-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | If a project or user sets a variable or cache entry named `C` or `CXX`, we were previously comparing those language names to the value of that variable, rather than the name itself. Double-quote the string to take advantage of policy `CMP0054`, but also add "x" prefixes to support projects that do not set the policy. This extends a similar fix from commit c8eb357738 (CompilerId: Tolerate variables named for languages, 2021-06-17, v3.21.0-rc1~9^2).
* | LCC: Disable Fortran preprocessor testing if unsupportedmakise-homura2023-02-161-2/+5
|/ | | | | | LCC < 1.24 has no way to disable integrated Fortran preprocessor, and it can't produce preprocessed files explicitly. So we disable all functionality (and therefore tests) related to it.
* LLVMFlang: Fix post-preprocess compile for fixed-form FortranDavid Truby2023-02-141-0/+1
| | | | | | | | | | | | LLVM Flang's preprocessor output is always valid fixed form Fortran with a fixed line length of 72. If an application tries to use fixed form with a different line length, this will fail in the post-preprocessing compilation step as they will pass a flag asking for a different fixed line length. To fix this we can pass -ffixed-line-length-72 to the post-preprocess compilation stage. This will be ignored when the input is free form Fortran, and force to a 72 line length when the input is fixed.
* LCC: Fix extraction of __LCC__ version componentsBrad King2023-02-132-8/+4
| | | | | Previously the logic only worked for major versions of the form `1.xx`. Fix it to work with versions `2.xx` and above.
* Merge topic 'android-ndk-legacy-toolchain' into release-3.26Brad King2023-02-071-1/+1
|\ | | | | | | | | | | | | cb0b9452e8 Android: Provide CMAKE_ANDROID_NDK_VERSION with NDK legacy toolchain file Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8170
| * Android: Provide CMAKE_ANDROID_NDK_VERSION with NDK legacy toolchain fileBrad King2023-02-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This variable has been provided since commit 746906242d (Android: Detect NDK version number, 2021-02-26, v3.20.0-rc3~1^2~3) when using CMake's NDK support or the modern NDK toolchain file. Since commit 005e2cdfb0 (Android: Do not use gold for ndk >= r22, 2021-02-26, v3.20.0-rc3~1^2) we need the value in our compiler/platform information files, so provide it when using the NDK legacy toolchain file too. Revert commit 1c86e397fe (Android/Clang: Tolerate undefined CMAKE_ANDROID_NDK_VERSION, 2022-09-16, v3.25.0-rc1~118^2) since the variable should now always be defined. Issue: #21772 Fixes: #24386
* | Modules: Record system inspection steps in the configure logBrad King2023-01-181-2/+2
| | | | | | | | | | | | | | | | Replace old-style `file(APPEND .../CMake{Output,Error}.log)` logging with calls to `message(CONFIGURE_LOG)` to record the steps in the `CMakeConfigureLog.yaml` configure log instead. Issue: #23200
* | IntelLLVM: Add provisional flags for C23 and C++23scivision2023-01-162-0/+12
| |
* | IntelLLVM: Replace -Qstd= with -Qstd: on Windowsscivision2023-01-161-6/+6
| | | | | | | | | | | | The latter is the documented form [1]. [1] https://www.intel.com/content/www/us/en/develop/documentation/oneapi-dpcpp-cpp-compiler-dev-guide-and-reference/top/compiler-reference/compiler-options/language-options/std-qstd.html
* | Merge topic 'IntelLLVM-msvc-no-cxx11'Brad King2023-01-131-2/+2
|\ \ | |/ | | | | | | | | | | 88f9fdcb03 IntelLLVM: Avoid unnecessary -Qstd=c++11 flag on Windows Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8069
| * IntelLLVM: Avoid unnecessary -Qstd=c++11 flag on WindowsBrad King2023-01-121-2/+2
| | | | | | | | | | | | | | | | The IntelLLVM compiler, for compatibility with MSVC on Windows, always runs with support for at least C++14. The `-Qstd=c++11` flag just causes a warning that it is unused. Fixes: #24316
* | Merge topic 'cuda-nvcc-cuda20'Brad King2022-12-141-0/+12
|\ \ | |/ | | | | | | | | | | 0aeeb8160c CUDA: Add support for cuda_std_20 for nvcc 12.0+ Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8008
| * CUDA: Add support for cuda_std_20 for nvcc 12.0+Robert Maynard2022-12-131-0/+12
| | | | | | | | CUDA 12.0 has been released with support for `-std=c++20`.
* | Clang-FindBinUtils: also find `clang-scan-deps`Ben Boeckel2022-12-021-0/+11
| | | | | | | | `clang-scan-deps` will be required for C++20 module scanning purposes.
* | Merge topic 'iar-rsp-on-objects'Brad King2022-11-291-22/+16
|\ \ | | | | | | | | | | | | | | | | | | a51e01f2ec IAR: Add response flag for files Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7957
| * | IAR: Add response flag for filesFelipe Torrezan2022-11-271-22/+16
| | |
* | | Merge topic 'msvc-cxx-no-optin-experimental-flag'Brad King2022-11-291-1/+0
|\ \ \ | |/ / |/| / | |/ | | | | | | | | 12e4bc73cb MSVC: don't opt into dyndep support Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7965
generated by cgit v0.12 at 2025-03-22 19:47:20 (GMT)