Shuenhoy/vtk-m
1
0
Fork 0
mirror of https://gitlab.kitware.com/vtk/vtk-m synced 2024-09-08 21:33:55 +00:00
Code Issues 2 Actions Packages Projects Releases Wiki Activity
9,024 Commits 9 Branches 24 Tags 36 MiB
dd2aa335e8
Commit Graph

40 Commits

Author SHA1 Message Date
Vicente Adolfo Bolea Sanchez
f60a45bc63 Enforce C++14 in the whole project 
Signed-off-by: Vicente Adolfo Bolea Sanchez <vicente.bolea@kitware.com>
 2021-04-12 13:29:46 -04:00
nadavi
a1c3752dfb split -Wchar-subscripts out from clang compile flags 2020-12-02 16:24:08 +00:00
Vicente Adolfo Bolea Sanchez
e3d7347080 IBM XL: disable unused-template pragma for xl 
Signed-off-by: Vicente Adolfo Bolea Sanchez <vicente.bolea@kitware.com>
 2020-08-21 15:40:05 -04:00
Robert Maynard
78a6631026 Correct cuda compiler flag ordering for clang as CUDA host compiler 2020-08-20 08:34:23 -04:00
Sujin Philip
452f61e290 Add Kokkos backend 2020-08-12 13:55:24 -04:00
Allison Vacanti
07b55a9546 Fix MSVC flags for CUDA builds. 
Fixes #443.
 2019-12-05 14:02:55 -05:00
Robert Maynard
1bfcce19dd VTK-m builds with separate function sections to allow smaller binaries 
Consumers of VTK-m when enabling of dropping of unused functions
will see VTK-m functions dropped. Previously this didn't happen
as VTK-m didn't build object files with the correct flags for this.

By allowing the linker to remove unused symbols we see a significant
saving the file size of VTK-m tests, examples, and benchmarks.
An OpenMP build of the tests and benchmarks goes from 168MB to
141MB which is roughly a 16% filesize reduction.

Initially I had presumed that these changes would increase link times.
But in measurements the total wall time for compilation of VTK-m has
stayed about the same ( seeing a decrease of 1.5% ). Presumably the
increased computation is offset by the reduction in file writing.
 2019-09-11 13:34:25 -04:00
Robert Maynard
267f963d32 Opt into all CMake 3.15 policies 2019-08-20 15:38:27 -04:00
Robert Maynard
736664612d Cleanup VTK-m warning flags and add in Wodr 
This was done to help us catch ODR violations quicker
 2019-07-18 13:33:18 -04:00
Robert Maynard
2a7ef30116 CMake: Don't presume the cuda compilers is always NVCC. 2019-05-29 09:24:01 -04:00
Robert Maynard
7184648c44 Add support for clang-cl compilation on windows 2019-05-14 11:47:21 -04:00
nadavi
fbcea82e78 conslidate the license statement 2019-04-17 10:57:13 -06:00
Robert Maynard
e5f1479e0d Wconversion won't be past to CUDA when it is using GCC. 2019-03-05 16:21:15 -05:00
Dave Pugmire
d974bcb5c3 fix for gcc4.8 2019-03-04 08:52:45 -05:00
Dave Pugmire
efbc8d68b4 Change compiler flags and undo conversions. 2019-03-01 15:25:48 -05:00
Robert Maynard
f1e1a524e9 Require CMake 3.8 to build VTK-m. 2019-01-09 16:01:22 -05:00
Robert Maynard
7a5e32be73 Update VTKmCompilerFlags to suppress stack-size-warnings on CUDA 9+ 
This will allow better suppression of cuda stack size warnings
for developers and build machines.
 2018-12-27 15:42:03 -05:00
Allison Vacanti
8baacca525 Link vtkm_developer_flags directly into vtkm libraries. 
This should properly propogate the flags to superprojects.
 2018-12-06 13:56:18 -05:00
Robert Maynard
dfa9f64436 MSVC now supports the COMPILE_LANGUAGE generator expression. 2018-11-12 15:16:13 -05:00
luz.paz
d5beb69ec1 Misc. typos 
Found via `codespell`
 2018-10-04 10:30:33 -04:00
Allison Vacanti
feb987fec2 Fix bad target name. 2018-07-11 11:02:13 -04:00
Allison Vacanti
e95734ef2d Fix compilation on ICC. Option/definition mismatch. 2018-07-10 10:48:19 -04:00
Robert Maynard
2ebde3806a Remove cyclic link between vtkm_developer_flags and vtkm_compiler_flags. 
Fixes #263
The vtkm_developer_flags target should only be to be consumed by
vtkm_compiler_flags.
 2018-07-09 08:27:41 -04:00
Sujin Philip
52758f7f3a Properly set up cuda architecture flags 2018-05-14 14:23:28 -04:00
Sujin Philip
d501a41576 Add VTKm_ENABLE_DEVELOPER_FLAGS cmake option 
The goal is to provide a way to disable VTK-m warning flags when used as a
thirdparty library.
VTK-m's stricter warning flags were cauing several new warnings in VTK.
 2018-05-10 12:47:20 -04:00
Robert Maynard
916c0902cf Correct Wstrict-overflow issues with gcc 5 and 6 2018-05-09 08:26:45 -04:00
Robert Maynard
c69fa0f39c Better document and consistently use vtkm compiler flag targets. 
We now consistently use vtkm_compiler_flags for external faces
flags, and vtkm_developer_flags for internal flags
 2018-05-08 17:38:35 -04:00
Robert Maynard
7c7b1ed54a Make sure when compiling CUDA code we suppress unknown pragma 2018-04-23 15:27:08 -04:00
Robert Maynard
4ca2522c6e VTK-m when building CUDA code in debug now checks for more warnings 2018-04-23 14:27:53 -04:00
Robert Maynard
5dfdc8304b Cuda will also print error/warning pragma values now. 
Previously we only printed out the error numbers on MSVC.
 2018-04-12 10:06:57 -04:00
Robert Maynard
022c987182 Correct warnings and errors found with MSVC2017+CUDA9 2018-01-31 15:58:45 -05:00
Robert Maynard
06da1528c4 vtk-m installed included directory obeys VTKm_INSTALL_INCLUDE_DIR 2018-01-16 15:42:38 -05:00
Robert Maynard
89ce1a34a0 Respect the settings of VTKm_Vectorization when building VTK-m 2018-01-16 15:42:37 -05:00
Robert Maynard
7c882473bd Correct compilation under MSVC when CUDA is enabled. 2018-01-16 15:42:37 -05:00
Robert Maynard
4a09615000 Correct issues when building on windows 2018-01-08 14:00:58 -05:00
Robert Maynard
5e1f7c60ad VTKm_INSTALL_ONLY_LIBRARIES allows installation of only vtk-m libs 2018-01-08 14:00:58 -05:00
Robert Maynard
afc19ab0fc Setup symbol visibility controls for VTK-m 2018-01-08 14:00:57 -05:00
Matthew Letter
16474bec53 Rename vtkm_debug_flags to vtkm_developer_flags closes #1 
This task came up after review with rob and ken for renaming the flags used in development build.
 2017-10-31 15:25:21 -06:00
Robert Maynard
ed8f4111ef Update all the code to work with CMake 3.3 
Obviously this does mean that CUDA is not supported with 3.3.
 2017-10-27 15:30:14 -04:00
Robert Maynard
56c7362258 A thought on what CMake 3.9 would mean to VTK-m. 2017-10-27 15:29:51 -04:00