summaryrefslogtreecommitdiff
path: root/Tests/FortranOnly
Commit message (Collapse)AuthorAgeFilesLines
* Tests: Bump CMake minimum required in tests to 3.5Brad King2023-03-011-1/+1
| | | | | | | | | | | | | | | | | | | CMake 3.27 deprecates compatibility with CMake < 3.5. Update tests that do not cover older interfaces to avoid the deprecation warning. Follow the pattern from: * commit 7b07ccdd2b (Tests/*Only: Update cmake_minimum_required versions, 2020-06-15, v3.19.0-rc1~629^2~1) * commit 72e7c45e98 (Tests: Bump CMake minimum required in tests to 2.8.12, 2020-12-22, v3.20.0-rc1~224^2) * commit f6b4db365a (Tests: bump cmake_minimum_required version to 2.8.12, 2021-04-04, v3.21.0-rc1~372^2) Also remove explicit `cmake_policy` settings made redundant by the version.
* LCC: Disable Fortran preprocessor testing if unsupportedmakise-homura2023-02-161-7/+10
| | | | | | 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.
* Tests: Avoid using CMake{Output,Error}.log filesBrad King2023-01-181-5/+17
| | | | These log files will soon go away, so avoid using them in tests.
* Ninja: Avoid preprocessing twice with explicit Fortran_PREPROCESSPeter Hill2022-02-242-1/+9
| | | | | | Fix spurious warnings from gfortran+Ninja for preprocessing. Fixes: #23248
* Tests: Fix FortranOnly test with Intel compiler on WindowsBrad King2021-04-281-0/+5
| | | | | The test regularly fails updating the `vc*.pdb` compiler-generated PDB file. Add the `/Z7` flag as the compiler suggests for this.
* Tests: Update for the Fujitsu compilerChuck Atkins2021-03-311-11/+10
|
* Tests: Update Fortran tests for IntelLLVMWilliam R. Dieter2021-01-281-2/+2
| | | | | | Update checks for the `Intel` compiler id to match `IntelLLVM` too. Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
* Tests: Update tests for NVHPC compilerTin Huynh2021-01-271-1/+1
| | | | Treat it just like PGI.
* Tests/*Only: Update cmake_minimum_required versionsBrad King2020-06-181-1/+1
| | | | Use 3.3 or 2.8.12 where possible.
* Ninja: Skip Fortran preprocessing if Fortran_PREPROCESS is OFFPeter Hill2020-05-211-24/+22
| | | | | | | | | If `Fortran_PREPROCESS` is explicitly turned off for a source file then we know it does not need to be preprocessed. Teach the Ninja generator to skip preprocessing in this case. Otherwise we still must preprocess just in case. Fixes: #18870
* Fortran: Add Fortran_PREPROCESS propertyPeter Hill2020-05-219-0/+71
| | | | Issue: #18870
* CheckFortranSource*: Avoid passing -DVAR to linkerBrad King2020-02-281-27/+23
| | | | | | | | The test project is compiled with a `-DVAR` compiler flag where `VAR` is the result variable. Tell `try_compile` to add the flag through `add_definitions` instead of `CMAKE_Fortran_FLAGS` so that it is not used for linking. Otherwise some Fortran compilers (e.g. XL 15) do not like the flag when used to drive linking.
* replace remove and remove_directory with rm in testsJohnny Jazeix2019-11-131-2/+2
|
* Ninja: Pass preprocessor definitions when compiling with Intel FortranBrad King2019-09-033-0/+14
| | | | | | | | The Intel Fortran compiler supports an extension that allows conditional compilation based on preprocessor definitions specified on the command line even when not preprocessing. Fixes: #19664
* VS: Fix Fortran target type selection with RC sourcesBrad King2019-03-012-1/+7
| | | | | | | | | | | | | The Intel Fortran `.vfproj` files do support both Fortran and the Windows Resource compiler (`.rc)` files. Prior to CMake 3.9 we did not support that, but commit 2c9f35789d (VS: Decide project type by linker lang as fallback, 2017-03-30, v3.9.0-rc1~340^2) accidentally enabled it. It was then broken by commit d3d2c3cd49 (VS: Fix Fortran target type selection when linking C++ targets, 2019-02-04, v3.14.0-rc1~13^2). Restore support for Fortran+RC in VS projects and add a test case. Fixes: #19002
* CheckFortranSourceRuns: Add module to check if Fortran code runsMichael Hirsch, Ph.D2019-01-101-2/+9
| | | | | Add a Fortran equivalent to the existing `Check{C,CXX}SourceRuns` modules.
* Various typo fixesLuz Paz2018-01-041-2/+2
| | | | Some are user-facing. Others are source comments.
* CheckFortranCompilerFlag: Add test caseBrad King2015-02-051-0/+7
| | | | Extend the FortranOnly test with a case covering this module.
* Makefile: Add assembly and preprocessed targets for FortranTim Gallagher2014-11-103-0/+38
| | | | Extend the FortranOnly test to cover "make <src>.i" targets.
* VS: Support Intel Fortran 15 .vfproj generation (#15175)Brad King2014-09-301-8/+9
| | | | | | | | | | | | | | | | This version of the Intel Fortran plugin to Visual Studio says: please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile) We must set TargetName and TargetExt in addition to the existing setting for OutputDirectory. The settings do not appear to hurt older versions of Intel Fortran, so set them unconditionally. Extend the FortranOnly test to cover a corresponding use case by using the OUTPUT_NAME target property. Inspired-by: Ian Harvey <Ian.Harvey@megms.com.au>
* Add CheckFortranSourceCompiles module (#14656)Brad King2014-08-181-0/+22
| | | | | | | Copy the CheckCSourceCompiles module and port it to Fortran. Extend the FortranOnly test to try using the new module. Suggested-by: Nicolas Bock <nicolasbock@gmail.com>
* Fortran: Add support for free- and fixed-form flagsBrad King2011-08-312-5/+7
| | | | | | | Define a "Fortran_FORMAT" target and source file property. Initialize the target property from a "CMAKE_Fortran_FORMAT" variable. Interpret values "FIXED" and "FREE" to indicate the source file format. Append corresponding flags to the compiler command line.
* Fix custom commands in VS2010 Fortran projects using CFG_INTDIR and test.Bill Hoffman2011-08-036-0/+73
For custom commands in VS2010 Fortran projects the INTDIR variable is different than in the rest of the solution because Intel fortran still uses the old VS project files even in VS2010. So, we replace $(Configuration) directly in the project files. I have also added a FortranOnly test that tests this feature and is run on any generator that has Fortran abilities.
View Lorry Controller Status