public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7880: Internal compiler error when passing template class to new operator Date: Thu, 21 Nov 2002 06:56:00 -0000 [thread overview] Message-ID: <20021115121604.1663.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7880; it has been noted by GNATS. From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: james@tga.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: celliott@tga.com Subject: Re: c++/7880: Internal compiler error when passing template class to new operator Date: Fri, 15 Nov 2002 14:08:20 +0100 Hi, the templates have nothing to do with the problems (I'll therefore change the synopsis of the PR). The testcase can be reduced to the following code snippet without templates that still crashes the compiler. ------------------------------snip here------------------------ typedef unsigned int size_t; struct A { ~A(); }; struct B { void operator delete (void *, A); void* operator new (size_t, A); B(); }; struct C { A bar(); }; void foo() { new(C().bar()) B; } ------------------------------snip here------------------------ With gcc 3.0.x - 3.2.1 I get the following ICE: PR7880.cc: In function `void foo()': PR7880.cc:23: Internal compiler error in convert_from_eh_region_ranges_1, at except.c:1404 Please submit a full bug report, [etc.] With gcc 2.95.3 I also get an ICE. The problem seems to be fixed in mainline. BTW, the bug has probably the same reason as PR 8582. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8582 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7880
next reply other threads:[~2002-11-15 12:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-21 6:56 Volker Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-13 7:54 nathan 2002-09-10 7:36 celliott
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=20021115121604.1663.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).