public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/6949: [2003-01-22] ICE in tsubst_decl, at cp/pt.c:5733 Date: Mon, 12 May 2003 17:06:00 -0000 [thread overview] Message-ID: <20030512170602.4266.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6949; it has been noted by GNATS. From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: gcc-prs@gcc.gnu.org, rubin@contractor.net, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/6949: [2003-01-22] ICE in tsubst_decl, at cp/pt.c:5733 Date: Mon, 12 May 2003 18:58:18 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6949 A further cleaned up testcase is below. The problem is that tsubst_decl expects non NULL DECL_TEMPLATE_INFO on the prototype declaration of the member function g in this assertion around line 6000 in cp/pt.c: | /* Nobody should be tsubst'ing into non-template functions. */ | my_friendly_assert (DECL_TEMPLATE_INFO (t) != NULL_TREE, 0); template<class T> void f(const T&) { struct B { void g (T); }; B b; }; void g() { f(42); } regards Christian
reply other threads:[~2003-05-12 17:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030512170602.4266.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.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).