public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Patrick Palka <ppalka@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: Patrick Palka <ppalka@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: use auto_vec in cp_parser_template_argument_list
Date: Tue, 9 Nov 2021 13:42:44 -0500 (EST)	[thread overview]
Message-ID: <5d4d91cf-7e0-921e-2345-734f671372e3@idea> (raw)
In-Reply-To: <a3d2d8c7-251d-7f10-beeb-ca5f36e50ff1@redhat.com>

On Tue, 9 Nov 2021, Jason Merrill wrote:

> On 11/9/21 11:02, Patrick Palka wrote:
> > Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
> 
> OK, though I wonder about using releasing_vec instead of auto_vec; reusing a
> previously allocated vec vs. building one on the stack.

Thanks a lot.  And hmm, I think using reusing a previously allocated vec
here would be tricky since cp_parser_template_argument_list can be
called recursively, and so only the outermost call would be able to
benefit from reuse unless we perhaps maintain a freelist of such vecs
IIUC.  Seems like that would complicate the code enough to not be worth
it.

> > gcc/cp/ChangeLog:
> > 
> > 	* parser.c (cp_parser_template_argument_list): Use auto_vec
> > 	instead of manual memory management.
> > ---
> >   gcc/cp/parser.c | 35 ++++++++---------------------------
> >   1 file changed, 8 insertions(+), 27 deletions(-)
> > 
> > diff --git a/gcc/cp/parser.c b/gcc/cp/parser.c
> > index 32de97b08bd..8823399529e 100644
> > --- a/gcc/cp/parser.c
> > +++ b/gcc/cp/parser.c
> > @@ -18558,11 +18558,6 @@ cp_parser_template_name (cp_parser* parser,
> >   static tree
> >   cp_parser_template_argument_list (cp_parser* parser)
> >   {
> > -  tree fixed_args[10];
> > -  unsigned n_args = 0;
> > -  unsigned alloced = 10;
> > -  tree *arg_ary = fixed_args;
> > -  tree vec;
> >     bool saved_in_template_argument_list_p;
> >     bool saved_ice_p;
> >     bool saved_non_ice_p;
> > @@ -18581,16 +18576,15 @@ cp_parser_template_argument_list (cp_parser*
> > parser)
> >     parser->non_integral_constant_expression_p = false;
> >       /* Parse the arguments.  */
> > +  auto_vec<tree, 10> args;
> >     do
> >       {
> > -      tree argument;
> > -
> > -      if (n_args)
> > +      if (!args.is_empty ())
> >   	/* Consume the comma.  */
> >   	cp_lexer_consume_token (parser->lexer);
> >           /* Parse the template-argument.  */
> > -      argument = cp_parser_template_argument (parser);
> > +      tree argument = cp_parser_template_argument (parser);
> >           /* If the next token is an ellipsis, we're expanding a template
> >            argument pack. */
> > @@ -18610,29 +18604,16 @@ cp_parser_template_argument_list (cp_parser*
> > parser)
> >             argument = make_pack_expansion (argument);
> >           }
> >   -      if (n_args == alloced)
> > -	{
> > -	  alloced *= 2;
> > -
> > -	  if (arg_ary == fixed_args)
> > -	    {
> > -	      arg_ary = XNEWVEC (tree, alloced);
> > -	      memcpy (arg_ary, fixed_args, sizeof (tree) * n_args);
> > -	    }
> > -	  else
> > -	    arg_ary = XRESIZEVEC (tree, arg_ary, alloced);
> > -	}
> > -      arg_ary[n_args++] = argument;
> > +      args.safe_push (argument);
> >       }
> >     while (cp_lexer_next_token_is (parser->lexer, CPP_COMMA));
> >   -  vec = make_tree_vec (n_args);
> > +  int n_args = args.length ();
> > +  tree vec = make_tree_vec (n_args);
> >   -  while (n_args--)
> > -    TREE_VEC_ELT (vec, n_args) = arg_ary[n_args];
> > +  for (int i = 0; i < n_args; i++)
> > +    TREE_VEC_ELT (vec, i) = args[i];
> >   -  if (arg_ary != fixed_args)
> > -    free (arg_ary);
> >     parser->non_integral_constant_expression_p = saved_non_ice_p;
> >     parser->integral_constant_expression_p = saved_ice_p;
> >     parser->in_template_argument_list_p = saved_in_template_argument_list_p;
> > 
> 
> 


  reply	other threads:[~2021-11-09 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 16:02 Patrick Palka
2021-11-09 16:59 ` Jason Merrill
2021-11-09 18:42   ` Patrick Palka [this message]
2021-11-10  5:16     ` Jason Merrill
2021-11-10 17:13       ` Patrick Palka

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=5d4d91cf-7e0-921e-2345-734f671372e3@idea \
    --to=ppalka@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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).