public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/42450] [4.5 Regression] another GCC 4.5 ICE on C++ templated code
Date: Fri, 22 Jan 2010 19:34:00 -0000 [thread overview]
Message-ID: <20100122193418.11508.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42450-18502@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from pinskia at gcc dot gnu dot org 2010-01-22 19:34 -------
(In reply to comment #5)
> Sorry for the probably uninformed question, but this bug was just tagged
> "enhancement", and I thought that "enhancement" meant "not really a bug but
> rather a feature request". I would like to understand?
I think it was an accident as this is a P1 bug anyways.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|enhancement |normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42450
next prev parent reply other threads:[~2010-01-22 19:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 18:55 [Bug c++/42450] New: " jacob dot benoit dot 1 at gmail dot com
2009-12-21 18:57 ` [Bug c++/42450] " jacob dot benoit dot 1 at gmail dot com
2009-12-21 22:04 ` hjl dot tools at gmail dot com
2009-12-29 17:27 ` jacob dot benoit dot 1 at gmail dot com
2009-12-30 20:56 ` [Bug middle-end/42450] [4.5 Regression] " rguenth at gcc dot gnu dot org
2010-01-02 16:07 ` rguenth at gcc dot gnu dot org
2010-01-04 9:38 ` dodji at gcc dot gnu dot org
2010-01-05 17:14 ` rth at gcc dot gnu dot org
2010-01-22 19:10 ` hubicka at gcc dot gnu dot org
2010-01-22 19:29 ` jacob dot benoit dot 1 at gmail dot com
2010-01-22 19:34 ` pinskia at gcc dot gnu dot org [this message]
2010-01-24 13:58 ` hubicka at ucw dot cz
2010-02-23 4:06 ` pinskia at gcc dot gnu dot org
2010-03-03 14:38 ` manu at gcc dot gnu dot org
2010-03-03 22:12 ` manu at gcc dot gnu dot org
2010-03-04 1:29 ` zsojka at seznam dot cz
2010-03-04 18:23 ` jamborm at gcc dot gnu dot org
2010-03-04 18:24 ` jamborm at gcc dot gnu dot org
2010-03-05 19:42 ` jamborm at gcc dot gnu dot org
2010-03-08 10:44 ` jamborm at gcc dot gnu dot org
2010-03-15 13:24 ` rguenth at gcc dot gnu dot org
2010-03-18 20:07 ` jamborm at gcc dot gnu dot org
2010-03-19 10:15 ` jamborm at gcc dot gnu dot org
2010-03-25 16:41 ` hjl 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=20100122193418.11508.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).