diff options
| author | Tom de Vries <tdevries@suse.de> | 2022-03-30 13:26:52 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2022-03-31 09:34:42 +0200 |
| commit | bf4832d6fa817f66009f100a9cd68953062add7d (patch) | |
| tree | 273c372bde40f66ab1ffc53de1cd749cc29f9df9 /gcc/function.cc | |
| parent | b75f996e846d079251f3a6134617f0405c3ed535 (diff) | |
| download | gcc-bf4832d6fa817f66009f100a9cd68953062add7d.zip gcc-bf4832d6fa817f66009f100a9cd68953062add7d.tar.gz gcc-bf4832d6fa817f66009f100a9cd68953062add7d.tar.bz2 | |
[nvptx] Fix ASM_SPEC workaround for sm_30
Newer versions of CUDA no longer support sm_30, and nvptx-tools as
currently doesn't handle that gracefully when verifying
( https://github.com/MentorEmbedded/nvptx-tools/issues/30 ).
There's a --no-verify work-around in place in ASM_SPEC, but that one doesn't
work when using -Wa,--verify on the command line.
Use a more robust workaround: verify using sm_35 when misa=sm_30 is specified
(either implicitly or explicitly).
Tested on nvptx.
gcc/ChangeLog:
2022-03-30 Tom de Vries <tdevries@suse.de>
* config/nvptx/nvptx.h (ASM_SPEC): Use "-m sm_35" for -misa=sm_30.
Diffstat (limited to 'gcc/function.cc')
0 files changed, 0 insertions, 0 deletions