public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/58806] New attribute for functions that access memory only through their arguments
Date: Tue, 22 Oct 2013 11:32:00 -0000	[thread overview]
Message-ID: <bug-58806-4-3O4rVxqzgD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58806-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58806

--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> You cannot find the PR because it's already implemented via the "fn spec"
> attribute (conveniently not user-accessible because bike-shedding about
> whether separate attributes are required).  The documentation resides
> in gimple.c:gimple_call_arg_flags,

Thanks, I knew of the EAF_* flags (none look that promising for my particular
use), but not of this "fn spec" attribute.

> and I _think_ it doesn't quite provide
> what you want as it was designed to help the context and flow-insensitive
> points-to analysis which doesn't benefit from "this call does not clobber
> or read from escaped memory".  But what it provides is "the argument to
> this function does not escape" which is important.

I locally changed the name to fn_spec so I could try it. Nothing helps for
comment #0. The combination EAF_NOCLOBBER | EAF_NOESCAPE (aka 'r') is enough to
optimize comment #1. However, EAF_NOCLOBBER is exactly the opposite of what I
want since the whole point of g is to write to its argument, and I don't see
why EAF_NOESCAPE should be necessary since there is no other call afterwards.

So I guess more flags (ECF_* since they wouldn't apply to a specific argument)
would be good. I tried the attributes nothrow,nonnull,leaf on comment #0
because that's what gcc puts on memcpy and gcc knows that memcpy(data,...)
doesn't change *p, but that didn't work, I should look at where exactly the
difference between memcpy and init plays a role.


  parent reply	other threads:[~2013-10-22 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-58806-4@http.gcc.gnu.org/bugzilla/>
2013-10-21  2:14 ` glisse at gcc dot gnu.org
2013-10-21  8:34 ` rguenth at gcc dot gnu.org
2013-10-22 11:32 ` glisse at gcc dot gnu.org [this message]
2013-10-22 14:58 ` glisse at gcc dot gnu.org
2013-10-22 20:27 ` glisse at gcc dot gnu.org
2024-04-09  3:51 ` pinskia at gcc dot gnu.org

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=bug-58806-4-3O4rVxqzgD@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).