public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jakub@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hamzy@us.ibm.com, jakub@gcc.gnu.org Subject: Re: c++/6316: trap when compiling file Date: Tue, 16 Apr 2002 14:43:00 -0000 [thread overview] Message-ID: <20020416214344.21061.qmail@sources.redhat.com> (raw) Synopsis: trap when compiling file State-Changed-From-To: open->analyzed State-Changed-By: jakub State-Changed-When: Tue Apr 16 14:43:44 2002 State-Changed-Why: Simplified into (at -O3): struct A { ~A() throw() {} }; template<typename T, typename U> struct B { U a; B(const T *); }; typedef B<char, A> C; struct D { D(); }; struct E { virtual ~E(); }; E *bar (); void foo () { E *a = bar (); } extern char *z []; E * bar () { struct F : public E { F () { for (int i = 0; i < 2; i++) C e = z[i]; } D x, y; }; return new F (); } http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6316
next reply other threads:[~2002-04-16 21:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-16 14:43 jakub [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-17 10:58 jakub 2002-04-16 10:16 jakub 2002-04-15 15:46 hamzy
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=20020416214344.21061.qmail@sources.redhat.com \ --to=jakub@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=hamzy@us.ibm.com \ /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).