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/30768] [4.3 regression]: ICE in ext/pb_ds/regression/list_update_data_map_rand.cc
Date: Wed, 14 Feb 2007 05:14:00 -0000	[thread overview]
Message-ID: <20070214051412.20035.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30768-507@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from mmitchel at gcc dot gnu dot org  2007-02-14 05:14 -------
It's certainly my responsibility to fix it.  

Personally, I don't think it's necessary to revert it, and I will try to get to
it soon, but if it's getting in other people's way, then we could potentially
revert.  As I mentioned upthread, I didn't see the test fail, but presumably
that's either me being a moron, or some environmental difference.

Keep after me about it.


-- 

mmitchel at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |mark at codesourcery dot com
                   |dot org                     |
             Status|NEW                         |ASSIGNED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30768


  parent reply	other threads:[~2007-02-14  5:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-11 23:47 [Bug c++/30768] New: " hp at gcc dot gnu dot org
2007-02-11 23:55 ` [Bug c++/30768] " mmitchel at gcc dot gnu dot org
2007-02-12  0:00 ` [Bug middle-end/30768] " pinskia at gcc dot gnu dot org
2007-02-12  0:22 ` hp at gcc dot gnu dot org
2007-02-12  0:23 ` hp at gcc dot gnu dot org
2007-02-12  0:55 ` pinskia at gcc dot gnu dot org
2007-02-14  5:08 ` hp at gcc dot gnu dot org
2007-02-14  5:14 ` mmitchel at gcc dot gnu dot org [this message]
2007-02-14 20:16 ` hp at gcc dot gnu dot org
2007-02-14 22:32 ` pinskia at gcc dot gnu dot org
2007-02-14 23:21 ` mmitchel at gcc dot gnu dot org
2007-02-14 23:54 ` dnovillo at gcc dot gnu dot org
2007-02-14 23:56 ` mark at codesourcery dot com
2007-02-15  0:11 ` bkoz at gcc dot gnu dot org
2007-02-15  0:13 ` bkoz at gcc dot gnu dot org
2007-02-15  0:14 ` bkoz at gcc dot gnu dot org
2007-02-15  1:31 ` hp at gcc dot gnu dot org
2007-02-15  1:39 ` hp at gcc dot gnu dot org
2007-02-15 12:41 ` rguenth at gcc dot gnu dot org
2007-02-15 16:06 ` pcarlini at suse dot de
2007-02-15 21:43 ` hp at gcc dot gnu dot org
2007-02-16  1:49 ` pinskia at gcc dot gnu dot org
2007-02-16  9:06 ` pcarlini at suse dot de
2007-02-16 12:35 ` dnovillo at gcc dot gnu dot org
2007-02-16 14:27 ` paolo at gcc dot gnu dot org
2007-02-16 14:29 ` pcarlini at suse dot de
2007-02-16 17:01 ` hp at gcc dot gnu dot org
2007-02-16 17:04 ` pcarlini at suse dot de
2007-02-18 23:28 ` pinskia at gcc dot gnu dot org
2007-02-18 23:31 ` pinskia at gcc dot gnu dot org
2007-02-23  0:07 ` pinskia at gcc dot gnu dot org
2007-02-25 17:42 ` 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=20070214051412.20035.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).