public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kloedej at knmi dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52594] no traceback expected for explicit fortran stop command combined with -fbacktrace Date: Fri, 16 Mar 2012 08:45:00 -0000 [thread overview] Message-ID: <bug-52594-4-nr68V0PXWh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52594-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594 --- Comment #2 from Jos de Kloe <kloedej at knmi dot nl> 2012-03-16 08:28:11 UTC --- Thanks for your answer. Using stop 0 or stop 1 would indeed be a way around, but the awkward thing is that I do have some requirements to produce different values for the exit status for different error conditions. So using stop 1 everywhere is no solution for me. 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.
next prev parent reply other threads:[~2012-03-16 8:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-15 18:47 [Bug fortran/52594] New: " kloedej at knmi dot nl 2012-03-15 18:59 ` [Bug fortran/52594] " burnus at gcc dot gnu.org 2012-03-16 8:45 ` kloedej at knmi dot nl [this message] 2012-03-16 11:37 ` burnus at gcc dot gnu.org 2012-03-16 11:49 ` kloedej at knmi dot nl 2012-06-06 7:48 ` jb at gcc dot gnu.org 2012-12-14 7:59 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-14 8:44 ` jb at gcc dot gnu.org 2012-12-14 8:47 ` Joost.VandeVondele at mat dot ethz.ch
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-52594-4-nr68V0PXWh@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).