public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/84595] Add __builtin_break() built-in for a breakpointing mechanism
[not found] <bug-84595-4@http.gcc.gnu.org/bugzilla/>
@ 2021-06-09 15:45 ` pinskia at gcc dot gnu.org
2021-06-09 16:31 ` segher at gcc dot gnu.org
2021-06-09 16:33 ` segher at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-06-09 15:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |christophe.leroy at csgroup dot eu
--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 99299 has been marked as a duplicate of this bug. ***
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c/84595] Add __builtin_break() built-in for a breakpointing mechanism
[not found] <bug-84595-4@http.gcc.gnu.org/bugzilla/>
2021-06-09 15:45 ` [Bug c/84595] Add __builtin_break() built-in for a breakpointing mechanism pinskia at gcc dot gnu.org
@ 2021-06-09 16:31 ` segher at gcc dot gnu.org
2021-06-09 16:33 ` segher at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: segher at gcc dot gnu.org @ 2021-06-09 16:31 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |segher at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-06-09
--- Comment #11 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(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-side implementation might not be possible
> on all targets given it might be dependent on OS and debugger preferences
> as well?
Generating a trap instruction is not. How that then will be handled by
something else is that something else's concern, yes :-)
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c/84595] Add __builtin_break() built-in for a breakpointing mechanism
[not found] <bug-84595-4@http.gcc.gnu.org/bugzilla/>
2021-06-09 15:45 ` [Bug c/84595] Add __builtin_break() built-in for a breakpointing mechanism pinskia at gcc dot gnu.org
2021-06-09 16:31 ` segher at gcc dot gnu.org
@ 2021-06-09 16:33 ` segher at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: segher at gcc dot gnu.org @ 2021-06-09 16:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
--- Comment #12 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(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 not have an OS (or *are* the OS), for
example.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-06-09 16:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-84595-4@http.gcc.gnu.org/bugzilla/>
2021-06-09 15:45 ` [Bug c/84595] Add __builtin_break() built-in for a breakpointing mechanism pinskia at gcc dot gnu.org
2021-06-09 16:31 ` segher at gcc dot gnu.org
2021-06-09 16:33 ` segher at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).