public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/16091] [3.4 regression] -fdump-tree-original broken by callgraph Date: Fri, 09 Jul 2004 08:43:00 -0000 [thread overview] Message-ID: <20040709084320.32164.qmail@sourceware.org> (raw) In-Reply-To: <20040620094403.16091.ebotcazou@gcc.gnu.org> ------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-07-09 08:43 ------- Not sure this will ever be fixed, but it's nonetheless a regression. -- What |Removed |Added ---------------------------------------------------------------------------- Summary|[3.4 only] -fdump-tree- |[3.4 regression] -fdump- |original broken by callgraph|tree-original broken by | |callgraph http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16091
next prev parent reply other threads:[~2004-07-09 8:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-20 9:44 [Bug c++/16091] New: " ebotcazou at gcc dot gnu dot org 2004-06-20 16:40 ` [Bug c++/16091] [3.4 only] " pinskia at gcc dot gnu dot org 2004-07-09 8:43 ` ebotcazou at gcc dot gnu dot org [this message] 2004-08-15 4:00 ` [Bug c++/16091] [3.4 regression] " pinskia at gcc dot gnu dot org 2004-08-17 6:28 ` mmitchel at gcc dot gnu dot 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=20040709084320.32164.qmail@sourceware.org \ --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).