Hi!

On 2022-03-31T09:40:47+0200, Tom de Vries via Gcc-patches 
<gcc-patches@gcc.gnu.org> wrote:
> 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 now <https://github.com/MentorEmbedded/nvptx-tools/pull/33>
'as: Deal with CUDA 11.0, "Support for Kepler 'sm_30' and 'sm_32'
architecture based products is dropped"' available for comment/testing.

> 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.

With that resolved in nvptx-tools, we may then revert these GCC-level
workarounds, GCC commit bf4832d6fa817f66009f100a9cd68953062add7d
"[nvptx] Fix ASM_SPEC workaround for sm_30", and
GCC commit 12fa7641ceed9c9139e2ea7b62c11f3dc5b6f6f4
"[nvptx] Use --no-verify for sm_30".  OK to push, once nvptx-tools ready?

> Use a more robust workaround: verify using sm_35 when misa=sm_30 is specified
> (either implicitly or explicitly).

Thanks for that suggestion!


Grüße
 Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955

Reply via email to