public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <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 09:46:00 -0000 [thread overview] Message-ID: <bug-46807-4-2u1hPJSY7P@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-01-07 09:27:50 UTC --- You don't need to reduce the testcase yourself (of course it is appreciated if you do), all you need is provide the preprocessed source. If we have a testcase and it is reproduceable, it will be marked as regression and categorized properly eventually.
next prev parent reply other threads:[~2011-01-07 9:28 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 2011-01-07 9:46 ` jakub at gcc dot gnu.org [this message] 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-2u1hPJSY7P@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: linkBe 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).