public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/57361] Remove self memory assignment
Date: Wed, 22 May 2013 08:35:00 -0000	[thread overview]
Message-ID: <bug-57361-4-coKQWJ9pJY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57361-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-05-22
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Assignment expansion makes this optimization:

  /* Optimize away no-op moves without side-effects.  */
  if (operand_equal_p (to, from, 0))
    return;

The operand_equal_p implementation looks safe at the moment (even in terms
of type-based aliasing rules).

I'd have done a more aggressive optimization in DSE, doing

  if (stmt_kills_ref_p (stmt, gimple_assign_rhs1 (stmt)))
    ... must be a self-assignment ...

which would definitely need extra care for self-assignments that change
the effective type of a memory location.  Though I have a hard time
creating a testcase that would exhibit sth like

  MEM[(struct X *)q_1] = MEM[(struct Y *)q_1];

which would change the dynamic type of *q_1 to X from Y.


  reply	other threads:[~2013-05-22  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 19:10 [Bug tree-optimization/57361] New: " glisse at gcc dot gnu.org
2013-05-22  8:35 ` rguenth at gcc dot gnu.org [this message]
2013-06-13 19:47 ` [Bug tree-optimization/57361] " glisse 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-57361-4-coKQWJ9pJY@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).