https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
Tom de Vries changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
--- Comment #7 from Tom de Vries ---
Author: vries
Date: Mon Sep 25 10:36:23 2017
New Revision: 253145
URL: https://gcc.gnu.org/viewcvs?rev=253145=gcc=rev
Log:
[nvptx] Add exit after call to noreturn function
2017-09-25 Tom de Vries
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
--- Comment #6 from Tom de Vries ---
(In reply to Tom de Vries from comment #2)
> Replacing trap with exit or ret (or adding it after trap), makes the sigsegv
> go away.
Nvidia suggested a workaround of adding exit after trap for this (PR81069
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
Thomas Schwinge changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
--- Comment #5 from Tom de Vries ---
(In reply to Alexander Monakov from comment #3)
> ptxas gets confused around loops lacking
> exit edges (and perhaps other "unusual" CFG structures). They can easily
> appear even in original source and do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
--- Comment #4 from Tom de Vries ---
(In reply to Tom de Vries from comment #2)
> Replacing trap with exit or ret (or adding it after trap), makes the sigsegv
> go away.
This problem goes away for ptxas -ori starting cuda 7.0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
Tom de Vries changed:
What|Removed |Added
CC||tschwinge at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80035
--- Comment #1 from Tom de Vries ---
Created attachment 40965
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40965=edit
pr58640.s
