public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/22156] [4.0/4.1/4.2 Regression] bit-field copying regressed
Date: Tue, 07 Feb 2006 09:26:00 -0000 [thread overview]
Message-ID: <20060207092628.5345.qmail@sourceware.org> (raw)
In-Reply-To: <bug-22156-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from mmitchel at gcc dot gnu dot org 2006-02-07 09:26 -------
Steven, if we increased the priority of the bug, what solution would you
envision? This is not in any way meant to be a rhetorical or sarcastic
question. My reading of the audit trail is that this bug is essentially a
feature request for a new optimization; given that, I don't think we can make
it release-critical. Am I misunderstanding?
Thanks,
-- Mark
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22156
next prev parent reply other threads:[~2006-02-07 9:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22156-6528@http.gcc.gnu.org/bugzilla/>
2005-10-13 21:06 ` [Bug middle-end/22156] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-10-27 20:32 ` pinskia at gcc dot gnu dot org
2005-10-30 23:32 ` pinskia at gcc dot gnu dot org
2006-02-05 21:21 ` [Bug middle-end/22156] [4.0/4.1/4.2 " steven at gcc dot gnu dot org
2006-02-07 9:26 ` mmitchel at gcc dot gnu dot org [this message]
2006-02-28 20:49 ` mmitchel at gcc dot gnu dot org
2006-05-25 2:45 ` mmitchel at gcc dot gnu dot org
2007-02-14 9:34 ` [Bug middle-end/22156] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-03-20 4:43 ` aoliva at gcc dot gnu dot org
2007-03-26 3:40 ` patchapp at dberlin dot org
2007-04-05 18:51 ` aoliva at gcc dot gnu dot org
2007-04-05 22:06 ` [Bug middle-end/22156] [4.0/4.1/4.2 " aoliva at gcc dot gnu dot org
2007-04-30 17:41 ` aoliva at gcc dot gnu dot org
2007-07-09 9:15 ` [Bug middle-end/22156] [4.0/4.1/4.2/4.3 " pinskia at gcc dot gnu dot org
2007-10-01 16:36 ` aoliva at gcc dot gnu dot org
2007-10-01 16:46 ` aoliva at gcc dot gnu dot org
2007-10-09 4:42 ` aoliva at gcc dot gnu dot org
2007-10-09 4:45 ` aoliva at gcc dot gnu dot org
2007-10-09 4:56 ` aoliva at gcc dot gnu dot org
2007-12-03 4:26 ` pinskia 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=20060207092628.5345.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).