This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/52594] no traceback expected for explicit fortran stop command combined with -fbacktrace
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 15 Mar 2012 18:57:49 +0000
- Subject: [Bug fortran/52594] no traceback expected for explicit fortran stop command combined with -fbacktrace
- Auto-submitted: auto-generated
- References: <bug-52594-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-03-15 18:57:49 UTC ---
Using the current GCC 4.6 (4.6.4 20120310), I get by default no backtrace. Only
with -fbacktrace, I indeed get a backtrace when using STOP 1 but not one for
STOP 0.
Solution: Use -fno-backtrace (which is the default in 4.6).
With GCC 4.7 (and 4.8) -fbacktrace is now enabled default. However, you no
longer get a backtrace for STOP 1 or ERROR STOP 1.
Thus, I think GCC 4.7 and 4.8 do what you want. (GCC 4.7.0 will be released in
the next days, 4.8 is the current developer version.)