public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@ticam.utexas.edu To: gcc-gnats@gcc.gnu.org Subject: c++/9453: [3.4 regression] ICE in is_specialization_of, at cp/pt.c:860 Date: Mon, 27 Jan 2003 16:06:00 -0000 [thread overview] Message-ID: <20030127160438.12301.qmail@sources.redhat.com> (raw) >Number: 9453 >Category: c++ >Synopsis: [3.4 regression] ICE in is_specialization_of, at cp/pt.c:860 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Mon Jan 27 16:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Wolfgang Bangerth >Release: unknown-1.0 >Organization: >Environment: 3.4 >Description: This is a regression on 3.4: ------------------------ template <typename> class X { private: struct Inner; template <typename R> friend typename X<R>::Inner * foo () { return 0; }; }; template class X<void>; struct U { void bar () { foo<void> (); }; }; ------------------------- g/a> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c bug33-1.cc bug33-1.cc: In function `typename X<R>::Inner* foo()': bug33-1.cc:6: internal compiler error: in is_specialization_of, at cp/pt.c:860 Please submit a full bug report, The code does compile with 3.2.2, so this is a regression. Presently, the code does not compile with 3.3, but that is a separate matter: Kriang has fixed this on the mainline, but apparently the fix has not been backported to 3.3, although the patch that caused this has been applied to 3.3. I'll contact him separately about this. W, >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-27 16:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-27 16:06 bangerth [this message] 2003-01-28 16:26 lerdsuwa 2003-01-31 12:36 Kriang Lerdsuwanakij 2003-04-08 14:20 bangerth
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=20030127160438.12301.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-gnats@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).