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: Fri, 16 Mar 2012 11:13:17 +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
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-03-16 11:13:17 UTC ---
(In reply to comment #2)
> Thanks for your answer.
> Using stop 0 or stop 1 would indeed be a way around
I am lost.
With GCC 4.6 and an explicit -fbacktrace, I *do* get a backtrace for any
nonzero integer/exit status in STOP/ERROR STOP. (And none for zero.)
In GCC 4.7 and 4.8 (which have -fbacktrace already implicitly), I *do* *not*
get a backtrace for STOP/ERROR STOP, independent whether the integer is nonzero
or not.
> Anyway, this bug is just a feature request, so it is up to you developers to
> decide if you want to implement this or not.
I still believe that GCC 4.7 and 4.8 handle it - by default - as you would
like.
(Cf. http://gcc.gnu.org/wiki/GFortranBinaries ; if you are under Linux, your
distribution will likely have some 4.7 packages available - either in some
special branch or in their development version, cf. also
http://gcc.gnu.org/wiki/GFortranDistros)