https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
--- Comment #12 from Segher Boessenkool ---
(In reply to H. Peter Anvin from comment #9)
> How is this different from raise(SIGTRAP);?
It does an architecture-specific trap instruction, not a SIGTRAP signal.
The former is useful even if you do n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
Segher Boessenkool changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
Andrew Pinski changed:
What|Removed |Added
CC||christophe.leroy at csgroup
dot eu
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
H. Peter Anvin changed:
What|Removed |Added
CC||hpa at zytor dot com
--- Comment #9 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
--- Comment #8 from Daniel Gutson ---
(In reply to Richard Biener from comment #7)
> I frequently use raise(SIGSTOP) ... (or x86 specific you can do asm ("int
> 3");
> or whatever that break thing was...
>
> Note I think that a compiler-only-sid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
Richard Biener changed:
What|Removed |Added
Component|tree-optimization |c
Severity|normal
