public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: bjs5075@rit.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/9960: g++ 3.2 Date: Wed, 05 Mar 2003 14:57:00 -0000 [thread overview] Message-ID: <20030305145720.14927.qmail@sources.redhat.com> (raw) Synopsis: g++ 3.2 State-Changed-From-To: open->closed State-Changed-By: bangerth State-Changed-When: Wed Mar 5 14:57:19 2003 State-Changed-Why: Confirmed. A reduced testcase is this: ---------------------- struct Base { void foo(); template<class I> void foo(); }; struct Derived : Base { void (*funcptr)(); void bar() { funcptr == foo; } }; ---------------------------- It fails with 2.95, 3.0 and 3.2: g/x> /home/bangerth/bin/gcc-3.2.2-pre/bin/c++ -c y.cc y.cc: In member function `void Derived::bar()': y.cc:12: Internal compiler error in decay_conversion, at cp/typeck.c:1679 However, it is already fixed in 3.3 and 3.4 Wolfgang http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9960
next reply other threads:[~2003-03-05 14:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-05 14:57 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-05 3:26 bjs5075
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=20030305145720.14927.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=bjs5075@rit.edu \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).