[Bug libfortran/63930] libgfortran should use 'abort ()' instead of 'exit (2)' for run-time errors

2015-09-04 Thread fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63930 Francois-Xavier Coudert changed: What|Removed |Added Status|WAITING |RESOLVED

[Bug libfortran/63930] libgfortran should use 'abort ()' instead of 'exit (2)' for run-time errors

2015-07-05 Thread fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63930 Francois-Xavier Coudert fxcoudert at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED

[Bug libfortran/63930] libgfortran should use 'abort ()' instead of 'exit (2)' for run-time errors

2015-07-05 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63930 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug libfortran/63930] libgfortran should use 'abort ()' instead of 'exit (2)' for run-time errors

2015-07-05 Thread anlauf at gmx dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63930 Harald Anlauf anlauf at gmx dot de changed: What|Removed |Added CC||anlauf at gmx dot de

[Bug libfortran/63930] libgfortran should use 'abort ()' instead of 'exit (2)' for run-time errors

2015-07-05 Thread anlauf at gmx dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63930 --- Comment #3 from Harald Anlauf anlauf at gmx dot de --- (In reply to Harald Anlauf from comment #2) I think that there is a fundamental need to rewrite the handling of runtime errors in gfortran. Since 4.7 I do often not get useful