This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/9186: async exception from a signal handler not working as before
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, rabins at msil dot sps dot mot dot com
- Date: 7 Jan 2003 00:56:04 -0000
- Subject: Re: target/9186: async exception from a signal handler not working as before
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, rabins at msil dot sps dot mot dot com, gcc-gnats at gcc dot gnu dot org
Synopsis: async exception from a signal handler not working as before
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Mon Jan 6 16:56:04 2003
State-Changed-Why:
Confirmed. The documentation of -fnon-call-exceptions seems
to imply that the program should work as expected. On the other
hand, this would be an interesting case for a language
lawyer -- I'd say this is just asking for too much.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9186