1. 23 Aug, 2018 1 commit
  2. 25 May, 2018 1 commit
    • Brad King's avatar
      CUDA: Drop unused/broken platform link flags placeholder · edf0ea9b
      Brad King authored
      The `<CMAKE_CUDA_LINK_FLAGS>` placeholder in CUDA rule variables comes
      from the `<CMAKE_CXX_LINK_FLAGS>` placeholder from which the CUDA rule
      variables were originally derived.  It is not a public interface for
      adding link flags so no projects should be using it.  It is needed for
      platform information modules to specify platform-specific link flags for
      the language.  None of our platform modules set it, so it is unused.
      Furthermore, it is broken as currently implemented.  Some of the
      contexts in which it is used need `-Xlinker` and some do not.
      Therefore it is not possible to use the placeholder at all.
      Simply remove it for now.  If some need for platform-specific CUDA link
      flags arises a new solution will be needed.
  3. 28 Mar, 2018 1 commit
    • Brad King's avatar
      CUDA: Pass host linker directories to device linker · 88c7abb7
      Brad King authored
      In some environments, libraries containing device code are installed in
      directories searched by the host linker but not passed by nvcc to
      nvlink.  Make these libraries available by explicitly passing the
      host linker search directories during device linking.
      Issue: #16317
  4. 13 Jun, 2017 1 commit
  5. 15 Feb, 2017 1 commit
    • Brad King's avatar
      CUDA: Fix default compiler flags on Windows · 55fb46d2
      Brad King authored
      Fix the default values of `CMAKE_CUDA_FLAGS[_<CONFIG>]` on Windows to
      make the host compiler flags match those produced for C++ by the
      `Platform/Windows-MSVC` module.  This makes the flags consistent with
      those used for C++.
  6. 14 Feb, 2017 1 commit
    • Brad King's avatar
      CUDA: Link to standard system libraries when linking as CUDA · 1c60231c
      Brad King authored
      On Windows with MSVC-like host compilers we must honor the standard
      libraries chosen by the `Platform/Windows-MSVC` module.  Otherwise C
      code linked into the CUDA binary that expects to have these libraries
      available may not link.
  7. 12 Jan, 2017 2 commits
    • Robert Maynard's avatar
      CUDA: Now pass correct FLAGS when device link cuda executables. · 8d1f9e5b
      Robert Maynard authored and Brad King's avatar Brad King committed
      Previously we had a two issues when building cuda executables
      that required separable compilation. The first was that we didn't
      propagate FLAGS causing any -arch / -gencode flags to be dropped, and
      secondly generators such as ninja would use the CXX language flags
      instead of CUDA when the executable was mixed language.
    • Brad King's avatar
      CUDA: Populate NVIDIA compiler information on Windows · 11551702
      Brad King authored
      Port Windows-specific compilation and linking rules over from the
      `Platform/Windows-MSVC` module and adapt it for NVIDIA CUDA.  On Windows
      nvcc and its host compiler (MSVC) do not understand or use options like
      `-fPIC` or `-std=`, so condition those out.