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 |WAITING
Last reconfirmed| |2015-07-05
CC| |fxcoudert at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
On the other hand, using exit() guarantees nicely closing the program, closing
files, etc. which is useful to users. abort()'ing is useful for power users,
but probably more confusing for other users: why is it aborting if it already
gave an error message? Bailing out with error message and non-zero error code
seems much more in line with what software generally does.
Using exit() is in line with what other Fortran compilers do for runtime
errors, and we have consistently done that for years, so I would be very
cautious about changing this behavior.
