https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97348
--- Comment #8 from CVS Commits ---
The master branch has been updated by Thomas Schwinge :
https://gcc.gnu.org/g:aa7874596b9f12b25a3214b0a143b040fafa1f10
commit r12-8113-gaa7874596b9f12b25a3214b0a143b040fafa1f10
Author: Thomas Schwinge
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97348
Thomas Schwinge changed:
What|Removed |Added
CC||tschwinge at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97348
--- Comment #6 from Tom de Vries ---
(In reply to CVS Commits from comment #4)
> Both build again cuda 9.1.
FWIW, tested post-commit against cuda 11.1, no issues found.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97348
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |11.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97348
--- Comment #4 from CVS Commits ---
The master branch has been updated by Tom de Vries :
https://gcc.gnu.org/g:383400a6078d75bbfa1216c9af2c37f7e88740c9
commit r11-3752-g383400a6078d75bbfa1216c9af2c37f7e88740c9
Author: Tom de Vries
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97348
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #1)
> Looking in the nvptx-as sources, we find a hard_coded default:
> ...
> const char *smver = "sm_30";
> ...
> and after changing that to sm_35, the conftest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97348
--- Comment #2 from Tom de Vries ---
Anyway, we should be able to work around this by having gcc explicitly pass -m
sm_35 to nvptx-as:
...
-#define ASM_SPEC "%{misa=*:-m %*}"
+#define ASM_SPEC "%{misa=*:-m %*; :-m sm_35}"
...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97348
Tom de Vries changed:
What|Removed |Added
Target||nvptx
--- Comment #1 from Tom de Vries
