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 14:58:00 -0000	[thread overview]
Message-ID: <bug-58806-4-GsvXTOFbaU@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 #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #3)
> I should look at where exactly the difference between memcpy and init plays a role.

It is in call_may_clobber_ref_p_1 that memcpy takes a shortcut: it only checks
for refs_may_alias_p_1 with its first argument, instead of going through the
usual intersection of clobber sets.


  parent reply	other threads:[~2013-10-22 14:58 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
2013-10-22 14:58 ` glisse at gcc dot gnu.org [this message]
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-GsvXTOFbaU@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).