Skip to main content

Browse the archive

Revision 738f3f23aa50749f27a0ee6ea61e7e0f7e52313a authored by Francisco Facioni on 19 February 2020, 17:33:35 UTC, committed by Brad King on 24 February 2020, 18:31:33 UTC 
Ninja: Do not use nvcc response files with non-nvcc tools
 
Since commit d91b5a72cd (Ninja: Add support for CUDA nvcc response
files, 2019-05-30, v3.15.0-rc1~8^2) we use NVCC's `--options-file`
option to avoid long link command lines via a response file.  However,
for non-device linking the host tools are used and the option does not
make sense.  Update the logic to use `--options-file` only for device
linking.  Linking with the host tools already has its own logic for
response files.

Fixes: #19954
1 parent ebea30a
Raw File
.gitattributes 
.gitattributes   export-ignore
.hooks*          export-ignore

# Custom attribute to mark sources as using our C code style.
[attr]our-c-style  whitespace=tab-in-indent  format.clang-format-6.0

# Custom attribute to mark sources as generated.
# Do not perform whitespace checks.  Do not format.
[attr]generated  whitespace=-tab-in-indent,-indent-with-non-tab -format.clang-format-6.0

bootstrap        eol=lf
configure        eol=lf
*.[1-9]          eol=lf
*.sh             eol=lf
*.sh.in          eol=lf

*.bat            eol=crlf
*.bat.in         eol=crlf
*.sln            eol=crlf
*.vcproj         eol=crlf

*.pfx            -text
*.png            -text
*.png.in         -text

*.c              our-c-style
*.cc             our-c-style
*.cpp            our-c-style
*.cu             our-c-style
*.cxx            our-c-style
*.h              our-c-style
*.hh             our-c-style
*.hpp            our-c-style
*.hxx            our-c-style
*.notcu          our-c-style

*.cmake          whitespace=tab-in-indent
*.rst            whitespace=tab-in-indent conflict-marker-size=79
*.txt            whitespace=tab-in-indent
back to top