public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Uecker <uecker@tugraz.at>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-optimization/109334: Improve computation for access attribute
Date: Sat, 28 Oct 2023 22:29:03 +0200	[thread overview]
Message-ID: <5a28c1c4d9a5c63d806f49198b5a8445537dab4d.camel@tugraz.at> (raw)
In-Reply-To: <0ebb3b58-e6dc-4147-aa24-d12c1516756f@gotplt.org>


Thanks, Sid!

(one comment below)

Am Donnerstag, dem 26.10.2023 um 07:51 -0400 schrieb Siddhesh Poyarekar:
> On 2023-10-26 04:37, Martin Uecker wrote:

> 
> >         /* ... and either PARM is void * or has a type that is complete and has a
> >   	 constant size... */
> >         && ((typesize && poly_int_tree_p (typesize))
> > @@ -1587,10 +1587,14 @@ parm_object_size (struct object_size_info *osi, tree var)
> >         unsigned argpos = 0;
> >   
> >         /* ... then walk through the parameters to pick the size parameter and
> > -	 safely scale it by the type size if needed.  */
> > +	 safely scale it by the type size if needed.
> > +
> > +	 TODO: we could also compute the size of VLAs where the size is
> > +	 given by a function parameter.  */
> 
> Isn't this testcase h() in builtin-dynamic-object-size-20.c?  If you're 
> referring to testcase i(), then maybe "where the size is given by a 
> non-trivial function of a function parameter, e.g.
> fn (size_t n, char buf[dummy(n)])."

h() is supported.  For i() we would need something as
__builtin_access__with_size to record the result of dummy().

But the comment refers to the simpler case:

fn (size_t n, char (*buf)[n])
	[[gnu::access(read_write, 2, 1)]]

This doesn't work because buf[n] does not have constant
size, but it could be made to work more easily because
the size is directly given by a function argument.

Martin


> 
> >         for (arg = fnargs; arg; arg = TREE_CHAIN (arg), ++argpos)
> > -	if (argpos == access->sizarg && INTEGRAL_TYPE_P (TREE_TYPE (arg)))
> > +	if (argpos == access->sizarg)
> >   	  {
> > +	    gcc_assert (INTEGRAL_TYPE_P (TREE_TYPE (arg)));
> >   	    sz = get_or_create_ssa_default_def (cfun, arg);
> >   	    if (sz != NULL_TREE)
> >   	      {
> > 
> 
> We rely on the frontend to make sure that the arg at sizarg is an 
> integral type.  OK.
> 
> Overall the change looks OK with a few nits I pointed out above.
> 
> Thanks,
> Sid


  parent reply	other threads:[~2023-10-28 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  8:37 Martin Uecker
2023-10-26 11:51 ` Siddhesh Poyarekar
2023-10-26 15:51   ` Richard Biener
2023-10-28 20:29   ` Martin Uecker [this message]
2023-10-29 12:15     ` Siddhesh Poyarekar

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=5a28c1c4d9a5c63d806f49198b5a8445537dab4d.camel@tugraz.at \
    --to=uecker@tugraz.at \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=siddhesh@gotplt.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: 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).