This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/84595] Add __builtin_break() built-in for a breakpointing mechanism
- From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 27 Feb 2018 20:39:50 +0000
- Subject: [Bug tree-optimization/84595] Add __builtin_break() built-in for a breakpointing mechanism
- Auto-submitted: auto-generated
- References: <bug-84595-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Compare with e.g. the G_BREAKPOINT macro within GNOME's GLib library, which has
accumulated a collection of platform-specific logic for C/C++ code that wants
to inject a breakpoint:
http://git.gnome.org/browse/glib/tree/glib/gbacktrace.h
(LGPLv2+ licensed)
I had a go at adding something similar to CPython:
https://bugs.python.org/issue9635
(albeit for fewer platforms)
It seems useful to have this in either the compiler or in GNU libc.