public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nathan@gcc.gnu.org,
	wanderer@rsu.ru
Subject: Re: c++/5123: tree check: expected identifier_node, have template_id_expr in build_component_ref, at cp/typeck.c:2133
Date: Wed, 02 Jan 2002 04:51:00 -0000	[thread overview]
Message-ID: <20020102125129.11487.qmail@sources.redhat.com> (raw)

Synopsis: tree check: expected identifier_node, have template_id_expr in build_component_ref, at cp/typeck.c:2133

State-Changed-From-To: analyzed->closed
State-Changed-By: nathan
State-Changed-When: Wed Jan  2 04:51:28 2002
State-Changed-Why:
    2002-01-02  Nathan Sidwell  <nathan@codesourcery.com>
    
    	PR c++/5123
    	* typeck.c (build_component_ref): Cope with a TEMPLATE_ID_EXPR.
    	(build_x_function_call): Cope with a COMPONENT_REF containing a
    	TEMPLATE_ID_EXPR.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5123


             reply	other threads:[~2002-01-02 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02  4:51 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-28 11:02 nathan
2001-12-18 15:34 nathan
2001-12-14 14:56 wanderer

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=20020102125129.11487.qmail@sources.redhat.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=wanderer@rsu.ru \
    /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: link
Be 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).