public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/29212] ICE with -fipa-pta
Date: Wed, 27 Sep 2006 04:57:00 -0000 [thread overview]
Message-ID: <20060927045722.19801.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29212-7559@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from bangerth at dealii dot org 2006-09-27 04:57 -------
Filing bug reports is certainly a good think no matter what happens:
a) If code is finally merged from the branch, we will have to go back to
these bug reports to make sure they're really fixed
b) If code is never merged, we at least have some sort of measure of how
broken a feature really is (see, for example, old -fnew-ra)
That said, I think the attitude "I'm not going to fix this since I may or
may not come around to merge some branch in the future" is not helpful. In
particular since this is going to be in a release at one point. Some more
convincing statement that for example "I've checked the branch and the
problem doesn't appear there; it is going to be merged for 4.3" would certainly
be nice...
W.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29212
next prev parent reply other threads:[~2006-09-27 4:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 13:14 [Bug tree-optimization/29212] New: " micis at gmx dot de
2006-09-25 13:16 ` [Bug tree-optimization/29212] " micis at gmx dot de
2006-09-25 14:17 ` micis at gmx dot de
2006-09-26 7:07 ` pinskia at gcc dot gnu dot org
2006-09-26 8:17 ` micis at gmx dot de
2006-09-27 2:14 ` dberlin at dberlin dot org
2006-09-27 4:57 ` bangerth at dealii dot org [this message]
2006-10-02 17:28 ` pinskia at gcc dot gnu dot org
2006-11-30 15:40 ` wouter dot vermaelen at pi dot be
2008-06-08 14:13 ` pinskia at gcc dot gnu dot org
2009-01-29 2:10 ` pinskia at gcc dot gnu dot org
2009-05-28 5:18 ` pinskia at gcc dot gnu dot org
2009-05-28 7:05 ` jv244 at cam dot ac dot uk
2010-05-03 7:46 ` jv244 at cam dot ac dot uk
2010-05-03 9:17 ` rguenth 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=20060927045722.19801.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: link
Be 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).