https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104758
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tschwinge at gcc dot gnu.org
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> With f.i. sm_30 triggering -Wa,--no-verify, we could work around the CUDA
> problem:
> ...
> diff --git a/gcc/config/nvptx/nvptx.h b/gcc/config/nvptx/nvptx.h
> index 4ab412bc7d8e..3ca22a595d20 100644
> --- a/gcc/config/nvptx/nvptx.h
> +++ b/gcc/config/nvptx/nvptx.h
> @@ -32,7 +32,7 @@
> /* Default needs to be in sync with default for misa in nvptx.opt.
> We add a default here to work around a hard-coded sm_30 default in
> nvptx-as. */
> -#define ASM_SPEC "%{misa=*:-m %*; :-m sm_35}"
> +#define ASM_SPEC "%{misa=*:-m %*; :-m sm_35}%{misa=sm_30:--no-verify}"
>
> #define TARGET_CPU_CPP_BUILTINS() nvptx_cpu_cpp_builtins ()
>
> ...
>
> We could do something similar by making nvptx-as.c detect the "SM version
> specified by .target is higher than default SM version assumed" problem and
> not error out, perhaps issue a warning, or deal with this at nvptx-tools
> configure time, similar to how that is done for ptxas unavailability.
>
Thomas, I'm currently testing the %{misa=sm_30:--no-verify} workaround. Do you
see a possibility to handle this in nvptx-tools instead ?
