public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com> To: "gcc-bugzilla@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org> Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org> Subject: Re: [Bug c++/35421] ICE on Valid Code Date: Mon, 03 Mar 2008 01:43:00 -0000 [thread overview] Message-ID: <24722D24-4F67-44DB-9628-0CBE81D1EE02@gmail.com> (raw) In-Reply-To: <20080303005453.9236.qmail@sourceware.org> Sent from my iPhone On Mar 2, 2008, at 16:54, "mckelvey at maskull dot com" <gcc-bugzilla@gcc.gnu.org > wrote: > > > ------- Comment #3 from mckelvey at maskull dot com 2008-03-03 > 00:54 ------- > (In reply to comment #2) >> Subject: Re: ICE on Valid Code >> >> >> A 65,000 line testcase? Seriously? >> > > I'll try to make a smaller one. But it most likely won't be small. > I think the bug is caused by a VERY large expression used with a > constructor > within a try-catch. > Most likely this is just a stack overflow so really not an interesting testcase. Thanks, Andrew Pinski >
next prev parent reply other threads:[~2008-03-03 1:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-02 22:57 [Bug c++/35421] New: " mckelvey at maskull dot com 2008-03-02 22:59 ` [Bug c++/35421] " mckelvey at maskull dot com 2008-03-02 23:21 ` brian at dessent dot net 2008-03-03 0:55 ` mckelvey at maskull dot com 2008-03-03 1:43 ` Andrew Pinski [this message] 2008-03-03 1:44 ` pinskia at gmail dot com 2008-03-03 3:32 ` dannysmith at users dot sourceforge dot net 2008-03-05 2:51 ` mckelvey at maskull dot com 2009-07-04 16:15 ` dave dot korn dot cygwin at gmail dot com 2009-12-25 22:11 ` paolo dot carlini at oracle dot com 2009-12-28 2:08 ` mckelvey at maskull dot com 2009-12-28 10:35 ` paolo dot carlini at oracle dot com
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=24722D24-4F67-44DB-9628-0CBE81D1EE02@gmail.com \ --to=pinskia@gmail.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-bugzilla@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).