public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/82885] memcpy does not propagate aliasing knowledge
Date: Sun, 01 Aug 2021 17:07:09 +0000	[thread overview]
Message-ID: <bug-82885-4-mEPfOqn4OG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82885-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82885

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|middle-end                  |tree-optimization
           Severity|normal                      |enhancement

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The original testcase is fixed in GCC 8+:
  <bb 2> [local count: 1073741825]:
  __builtin_memcpy (ch1_3(D), ch2_4(D), 1048576);
  _1 = MEM[(const char *)ch2_4(D) + 2B];
  *ch1_3(D) = _1;
  MEM[(char *)ch1_3(D) + 1B] = _1;

fre1 is able to figure this out but this is not exactly propagating aliasing
info, just that the value of ch2[2] cannot change if ch1[0] is stored with the
same value of what was in ch2[2]; memcpy is not needed to show that :).

A better testcase which shows there is still a missing aliasing case:
void foo3(char* ch1, char* ch2) {
    __builtin_memcpy(ch1, ch2, 1024*1024);
    ch1[0] = ch2[2] + 1;
    ch1[1] = ch2[2];
}

           reply	other threads:[~2021-08-01 17:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-82885-4@http.gcc.gnu.org/bugzilla/>]

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-82885-4-mEPfOqn4OG@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).