| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
If the CUDA version macros are not defined, run `nvcc --version` and
extract the version from its output.
Fixes: #17920
|
|
|
|
|
| |
Add CMAKE_DEPFILE_FLAGS_${lang} to SunPro and XL. These flags are used
by the Ninja generator.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
3f82c5904d Clang: Add standard flags support when simulating MSVC
8381bc12ad Clang: Avoid extra C++ feature detection when simulating MSVC
6cddf7ba32 Clang: Refactor standard flags logic when simulating MSVC
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1906
|
| |
| |
| |
| |
| |
| |
| | |
When Clang 3.9 simulates MSVC 19.0 or higher it knows the `-std:` flags
that such versions of MSVC defines.
Fixes: #17866
|
| |
| |
| |
| |
| |
| |
| |
| | |
Apply the optimization from commit v3.10.0-rc1~131^2 (MSVC: Avoid
unnecessary C++ feature detection steps, 2017-09-11) to the case of
Clang simulating a version of MSVC that does not define standards.
Issue: #17274
|
| |
| |
| |
| |
| | |
Consolidate the compile options and standard defaults branches.
Add comments.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
5f4272cc06 Features: Record for VS 2017 through 15.6
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1903
|
| |
| |
| |
| |
| |
| |
| | |
VS 15.3 has more features than we recorded in commit v3.7.0-rc1~156^2~2
(Features: Record features for VS 15 Preview 4, 2016-09-05).
While at it, update comments and simplify some cases.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Android NDK r16b comes with
Android clang version 5.0.300080 (based on LLVM 5.0.300080)
Although it claims version 5, it does not support the `-std=c++17`
or `-std=c++2a` flags that upstream Clang does.
Android NDK r17-beta1 comes with
Android (4639204 based on r316199) clang version 6.0.1
that does have the flags.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
8570dc7f64 Help: Update compiler versions in cmake-compile-features.7.rst
874d3d2948 Help: Add release note for C++ 20 support
7f295b1bd3 Features: Activate C++ 20 support for Clang 5.0+
71cb8ce3a1 Features: Activate C++ 20 support for GNU 8.0+
8f146c4508 Features: Activate C++ 20 support for MSVC 19.12.25835+
7fe580a362 Features: Add infrastructure for C++ 20 language standard
1b328e09a3 Features: Use -std=c++17 for C++ 17 on Clang 5.0+
0bc3e5788a Features: Use -std=c++17 for C++ 17 on GNU 8.0+
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1892
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Issue: #17849
|
| | |
| | |
| | |
| | | |
Clang 5.0 added support for the `-std=c++17` flag.
|
| |/
| |
| |
| | |
GNU 8 now documents official support for the `-std=c++17` flag.
|
|/
|
|
|
|
|
|
|
| |
The MSVC C compiler has no notion of C language standards or flags.
Tell CMake to assume that all language standards are available.
Record available C language features depending on the version of
the compiler.
Fixes: #17858
|
|
|
|
| |
Oracle Developer Studio 12.6 adds support for more C++ 11 features.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Features recorded by commit v3.6.0-rc1~120^2~5 (Features: Record
standards and features for Intel C++ on UNIX, 2016-04-28) for the Intel
compiler left out initializer list support because our test case in
`Tests/CompileFeatures/cxx_generalized_initializers.cpp` caused an
internal compiler error. It turns out this is because the Intel
compiler asserts the `initializer_list` constructor signatures to verify
that they match its own `<initializer_list>` header. It was our dummy
implementation used to test the language feature without any headers
that caused the ICE. Revise it to use a constructor signature accepted
by the Intel compiler.
Fixes: #17829
|
|\
| |
| |
| | |
Merge-request: !1831
|
| |
| |
| |
| |
| |
| |
| | |
The nvcc compiler does not support `@<rspfile>` arguments. It does
offer a `--options-file` argument that can be investigated later.
Fixes: #17797
|
|/
|
|
|
|
|
|
|
| |
IBM XL C/C++ for Linux versions 13.1.6 and above no longer define
`__IBMC__` or `__IBMCPP__` by default (see `-qxlcompatmacros`).
Instead `__ibmxl__` now identifies the compiler along with some
related new version macros.
Fixes: #17784
|
|
|
|
|
|
|
|
| |
In commit v3.11.0-rc1~466^2 (Compiler/TI: Add support for depfile
generation for Ninja, 2017-10-16) the flag for C++ was added in a
variable with a typo in its name. Fix the spelling.
Issue: #17360
|
|\
| |
| |
| |
| |
| |
| |
| | |
c3d576f5 Intel: Add C++17 compiler options
4a5727d3 Intel: Correct the C11 ext flag
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1711
|
| |
| |
| |
| |
| |
| |
| | |
Since Intel C++ 18.0, some C++17 features are supported if the flags
-std=c++17, respectively /Qstd=c++17 are given.
Fixes: #17687
|
| |
| |
| |
| | |
Intel does not support a 'gnu11' standard flag, only 'c11'.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
c4dc6485 XL: Enable use of response files for includes and objects
e342e410 Makefile,Ninja: Use tool-specific response file flag for include dirs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1691
|
| |/
| |
| |
| |
| | |
The IBM XL compiler supports response files via `-qoptfile=<file>`
instead of `@<file>`.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
b886b46c Cray: Add common PIC flags
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1692
|
| |
| |
| |
| | |
Fixes #17208
|
| |
| |
| |
| |
| |
| |
| |
| | |
The `CMakeASMInformation` module warns when no compiler-specific module
is found for the `ASM` language. Add a minimal `Compiler/MSVC-ASM`
module to avoid the warning for MSVC.
Fixes: #17532
|
| |
| |
| |
| | |
Some are user-facing. Others are source comments.
|
|\ \
| |/
| |
| |
| |
| |
| | |
e4707048 IAR: FindBinUtils should work for CXX as well as C
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1572
|
| |
| |
| |
| |
| |
| | |
The IAR compiler test works when a project specifies LANGUAGES C CXX
but fails if CXX comes before C. This change makes it work regardless
of the order.
|
| |\
| | |
| | |
| | | |
Merge-request: !1435
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !1393
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
3c368228 Flang: Add support for compiling sources on Windows
72d27964 Flang: Identify as simulating MSVC on Windows
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1430
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In `CMakeFortranCompilerId.F.in`, take the `_MSC_VER` out of the
Intel-specific block so it will trigger for other compilers like Flang.
In `Compiler/Clang.cmake`, switch off Fortran too.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some are user facing.
Found using
codespell -q 3 --skip="./Utilities" -I .cmake-whitelist.txt`
whereby the whitelist contained:
ans
dum
helpfull
emmited
emmitted
buil
iff
isnt
nto
ot
pathes
substract
te
todays
upto
whitespaces
|
|\ \ \ \ \
| |/ / / /
|/| | | /
| | |_|/
| |/| |
| | | |
| | | | |
f86879a0 Record C compile features flags for MinGW Clang on Windows
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1435
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was done for C++ by commit v3.5.0-rc1~69^2 (Record compile features
for MinGW Clang on Windows, 2016-01-11). Make the same change for C.
The `UNIX` condition on Clang C compiler features was already dropped by
refactoring in commit v3.9.0-rc1~17^2~4 (Compilers: Port to use default
cmake_record_lang_compile_features macros, 2017-05-10).
Our documentation already claims support for this combination. This
was simply an oversight when support was added for MinGW Clang C++.
Issue: #15897
Issue: #15943
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
3aeff21d Flang: Remove unsupported fbounds-check flag
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1393
|
| |/ /
| | |
| | |
| | |
| | | |
The Flang compiler neither supports nor documents -fbounds-check leading
to -Wunused-command-line-argument warnings with the default Debug flags.
|
| |/
|/|
| |
| |
| |
| |
| | |
TI C/C++ compiler are now able to generate dependency files during
compilation.
Fixes: #17360
|
|/
|
|
|
|
|
|
| |
In the normal archiving rules the ``<CMAKE_AR>`` placeholder is replaced
by the generators with a properly-quoted path to the tool. In the IPO
rules we specify the tools directly, so we need to quote them.
Fixes: #17326
|
|
|
|
|
|
|
|
| |
`__IAR_SYSTEMS_ICC__` provides additional version information that
we need to determine correct usage of the compiler. Extract and
store it as `CMAKE_<LANG>_COMPILER_VERSION_INTERNAL`.
Issue: #17264
|
|
|
|
|
|
|
|
|
| |
Starting in CUDA 9 the default compilation mode is C++14, and you need
to explicitly enable C++98/03 mode.
While at it, document `14` among the values for `CUDA_STANDARD`. This
was accidentally left out of commit v3.9.0-rc1~118^2 (CUDA: Add support
for the C++14 standard flag, 2017-05-11).
|
|\
| |
| |
| |
| |
| |
| |
| | |
485a6f0e PGI-Fortran: Add -Mipa=fast,inline as IPO option.
97f0b177 PGI-Fortran: Remove -Kieee and -Mpreprocess
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1239
|
| |
| |
| |
| |
| |
| |
| | |
Remove -Mipa=fast as a default flag and add it as an option instead.
-Mipa=fast is a flag that speeds up runtime but at the cost of significant
compile time increase and therefore, shouldn't be a default flag.
In addition, -Mipa isn't supported on PGI OpenPOWER or x86/llvm compilers.
|
| |
| |
| |
| | |
Fixes #17209
|