public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47893] [4.6 Regression] 4.6 miscompiles mesa on i686
Date: Fri, 25 Feb 2011 16:43:00 -0000 [thread overview]
Message-ID: <bug-47893-4-d8FF3tX0kl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47893-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47893
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> 2011-02-25 16:40:56 UTC ---
My temptation would be to revert until someone can get in there and design
things so that we either have a single list or there's clear rules for
manipulating objects in each list and reflecting the necessary information back
and forth.
Even with Jakub's suggestions my worry is other similar, subtle bugs are in
there and will bite us later.
next prev parent reply other threads:[~2011-02-25 16:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 12:48 [Bug middle-end/47893] New: " jakub at gcc dot gnu.org
2011-02-25 12:56 ` [Bug middle-end/47893] " jakub at gcc dot gnu.org
2011-02-25 13:07 ` rguenth at gcc dot gnu.org
2011-02-25 13:15 ` jakub at gcc dot gnu.org
2011-02-25 16:06 ` jakub at gcc dot gnu.org
2011-02-25 16:41 ` bernds at gcc dot gnu.org
2011-02-25 16:41 ` jakub at gcc dot gnu.org
2011-02-25 16:43 ` law at redhat dot com [this message]
2011-02-25 17:31 ` bernds at gcc dot gnu.org
2011-02-25 17:36 ` bernds at gcc dot gnu.org
2011-02-25 18:31 ` jakub at gcc dot gnu.org
2011-02-25 19:04 ` jakub at gcc dot gnu.org
2011-02-25 19:26 ` jakub at gcc dot gnu.org
2011-02-26 14:33 ` jakub at gcc dot gnu.org
2011-02-28 17:11 ` jakub at gcc dot gnu.org
2011-02-28 17:30 ` jakub 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-47893-4-d8FF3tX0kl@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: 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).