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,
	jkanze@caicheuvreux.com, nathan@gcc.gnu.org
Subject: Re: c++/9708: Unifies non-constant
Date: Mon, 24 Mar 2003 17:47:00 -0000	[thread overview]
Message-ID: <20030324174657.29275.qmail@sources.redhat.com> (raw)

Synopsis: Unifies non-constant

State-Changed-From-To: analyzed->closed
State-Changed-By: nathan
State-Changed-When: Mon Mar 24 17:46:57 2003
State-Changed-Why:
    2003-03-22  Nathan Sidwell  <nathan@codesourcery.com>
    
    	PR c++/9978, c++/9708
    	* cp-tree.h (instantiate_template): Add tsubst_flags parameter.
    	* call.c (add_template_candidate_real): Adjust
    	instantiate_template call.
    	* class.c (resolve_address_of_overloaded_function): Likewise.
    	* decl.c (build_enumerator): Set TREE_CONSTANT.
    	* pt.c (check_instantiated_args): New.
    	(push_inline_template_parms_recursive): Set TREE_CONSTANT,
    	TREE_READONLY.
    	(build_template_parm_index): Copy TREE_CONSTANT, TREE_READONLY.
    	(reduce_template_parm_level): Likewise.
    	(process_template_parm): Likewise.
    	(check_explicit_specialization): Adjust instantiate_template call.
    	(convert_template_argument): Don't check non-type argument here.
    	(lookup_template_class): Check them here.
    	(tsubst_friend_function): Adjust instantiate_template call.
    	(instantiate_template): Add tsubst_flags parameter, use it. Check
    	instantiated args.

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


             reply	other threads:[~2003-03-24 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 17:47 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-21 15:52 nathan

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=20030324174657.29275.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=jkanze@caicheuvreux.com \
    /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).