[Bug c++/70387] -fnon-call-exceptions has no effect

2017-03-28 Thread jwjagersma at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70387 --- Comment #5 from jwjagersma at gmail dot com --- Bumping this, I hope it will be resolved someday. I found a reference to the same issue, with another test case using posix signal handlers: https://cygwin.com/ml/cygwin/2010-07/msg00195.html

[Bug c++/70387] -fnon-call-exceptions has no effect

2016-03-25 Thread jwjagersma at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70387 --- Comment #4 from jwjagersma at gmail dot com --- Created attachment 38096 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38096=edit Test case 2 Generic test case, which doesn't require djgpp or a DOS machine. (Assuming throwing from

[Bug c++/70387] -fnon-call-exceptions has no effect

2016-03-25 Thread jwjagersma at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70387 --- Comment #3 from jwjagersma at gmail dot com --- Possibly interesting observation; the exception can be caught when using a pointer as divisor: int i = 0; int* volatile p = try { std::cout << 1 / *p << std::endl; } catch (std::exception&

[Bug c++/70387] -fnon-call-exceptions has no effect

2016-03-24 Thread jwjagersma at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70387 --- Comment #2 from jwjagersma at gmail dot com --- Created attachment 38077 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38077=edit Test case I reduced my code to the bare minimum required to reproduce this issue. Compile with djgpp:

[Bug c++/70387] -fnon-call-exceptions has no effect

2016-03-24 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70387 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|