public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwgk at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46807] internal compiler error: in synthesized_method_walk
Date: Fri, 07 Jan 2011 05:40:00 -0000	[thread overview]
Message-ID: <bug-46807-4-AYC5tMJcpO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46807-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from rwgk at yahoo dot com 2011-01-07 04:28:46 UTC ---
I just saw the "GCC 4.6.0 Status Report (2011-01-04), Stage 3 is over"
announcement.

This bug should be a P1 since it is an ICE on valid code.

If necessary I'll try to reduce the reproducer, but since that is likely
to be a significant effort, I'd like to be sure that someone is paying
attention. Is there?


  parent reply	other threads:[~2011-01-07  4:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05  7:40 [Bug c++/46807] New: " rwgk at yahoo dot com
2010-12-05  7:42 ` [Bug c++/46807] " rwgk at yahoo dot com
2010-12-17 22:34 ` rwgk at yahoo dot com
2010-12-17 22:38 ` pinskia at gcc dot gnu.org
2011-01-07  5:40 ` rwgk at yahoo dot com [this message]
2011-01-07  9:46 ` jakub at gcc dot gnu.org
2011-01-07 18:32 ` rwgk at yahoo dot com
2011-01-07 18:36 ` rwgk at yahoo dot com
2011-01-07 18:38 ` [Bug c++/46807] [4.6 Regression] " redi at gcc dot gnu.org
2011-01-07 19:42 ` redi at gcc dot gnu.org
2011-01-08  4:44 ` hjl.tools at gmail dot com
2011-01-14 14:24 ` rguenth at gcc dot gnu.org
2011-01-19 17:00 ` rguenth at gcc dot gnu.org
2011-01-19 20:30 ` jakub at gcc dot gnu.org
2011-01-21 19:46 ` jason at gcc dot gnu.org
2011-02-11 23:27 ` jason at gcc dot gnu.org
2011-02-14  8:24 ` ebotcazou at gcc dot gnu.org
2011-02-16  0:53 ` jason at gcc dot gnu.org
2011-02-16  5:08 ` rwgk at yahoo dot com
2011-02-16  7:06 ` 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-46807-4-AYC5tMJcpO@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).