public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, giovannibajo@libero.it, nobody@gcc.gnu.org Subject: Re: c++/10716: ICE in tree check: expected var_decl, have error_mark in tsubst_decl, at cp/pt.c:5987 Date: Sun, 18 May 2003 17:28:00 -0000 [thread overview] Message-ID: <20030518172832.4969.qmail@sources.redhat.com> (raw) Synopsis: ICE in tree check: expected var_decl, have error_mark in tsubst_decl, at cp/pt.c:5987 State-Changed-From-To: open->analyzed State-Changed-By: cae State-Changed-When: Sun May 18 17:28:32 2003 State-Changed-Why: Redux: template <bool Cond> struct A { }; template <typename p> struct B { typedef int car; }; template <typename Top> struct C { template <int pos> typename B<typename A<INVALID>::result>::car f (); }; C<int> x; I get a different message with 3.3-release due to a missing --enable-checking. This redux also ICEs 3.4 but at a different line number. Output of 3.3 WITHOUT treecheck output: 10716.cc: In instantiation of `C<int>': 10716.cc:10: instantiated from here 10716.cc:8: error: `INVALID' was not declared in this scope 10716.cc:8: confused by earlier errors, bailing out Output of somewhat dated 3.4 WITH tree checking: 10716.cc:8: error: `INVALID' has not been declared 10716.cc:8: error: template argument 1 is invalid 10716.cc:8: internal compiler error: tree check: expected class 't', have 'x' ( error_mark) in make_typename_type, at cp/decl.c:5498 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. regards Christian http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10716
next reply other threads:[~2003-05-18 17:28 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-18 17:28 ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-09 16:46 giovannibajo
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=20030518172832.4969.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=giovannibajo@libero.it \ --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).