https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859
--- Comment #7 from Martin Liška ---
Yep, let's forget about it ;)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859
--- Comment #6 from rguenther at suse dot de ---
On Mon, 17 Jul 2017, marxin at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859
>
> Martin Liška changed:
>
>What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859
Richard Biener changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859
Richard Guenther rguenth at gcc dot gnu.org changed:
What|Removed |Added
CC||hjl.tools at
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-08-26 21:18 ---
SIGABRT is not an async signal. It is one of the few signal that is not.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859
--- Comment #2 from rguenth at gcc dot gnu dot org 2006-08-26 21:25 ---
http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html
All functions not in the above table are considered to be unsafe with
respect to signals. In the presence of signals, all functions
