public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Melven.Roehrig-Zoellner at DLR dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65996] [5/6 Regression] gfortran ICE with -dH Date: Mon, 04 May 2015 12:14:00 -0000 [thread overview] Message-ID: <bug-65996-4-YDlmiFHe2I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65996-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65996 --- Comment #8 from Melven.Roehrig-Zoellner at DLR dot de --- Thanks for the quick replies and the discussion about the "not-so-usefulness" of the -dH switch (at least for our project). We most probably used this switch by mistake - you might possibly improve the documentation by adding "-dH Produce a core dump whenever a *compilation* error occurs." to prevent further misunderstandings for people who don't read the full paragraph.
next prev parent reply other threads:[~2015-05-04 12:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65996-4@http.gcc.gnu.org/bugzilla/> 2015-05-04 8:48 ` [Bug fortran/65996] [5 " jakub at gcc dot gnu.org 2015-05-04 9:50 ` dominiq at lps dot ens.fr 2015-05-04 9:58 ` jakub at gcc dot gnu.org 2015-05-04 10:20 ` Melven.Roehrig-Zoellner at DLR dot de 2015-05-04 10:37 ` jakub at gcc dot gnu.org 2015-05-04 10:46 ` dominiq at lps dot ens.fr 2015-05-04 10:53 ` jakub at gcc dot gnu.org 2015-05-04 12:14 ` Melven.Roehrig-Zoellner at DLR dot de [this message] 2015-07-16 9:10 ` [Bug fortran/65996] [5/6 " rguenth at gcc dot gnu.org 2015-10-16 8:31 ` rguenth at gcc dot gnu.org
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-65996-4-YDlmiFHe2I@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).