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/28134] optimize redundant memset + assignment
Date: Sat, 24 Dec 2011 03:16:00 -0000	[thread overview]
Message-ID: <bug-28134-4-lEJMCXGPRr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28134-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011-12-24
            Version|unknown                     |4.7.0
     Ever Confirmed|0                           |1

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-12-24 03:11:54 UTC ---
Confirmed:
<bb 2>:
  memset (bp_2(D), 0, 24576);

<bb 3>:
  # ivtmp.14_9 = PHI <ivtmp.14_20(3), 0(2)>
  MEM[base: bp_2(D), index: ivtmp.14_9, offset: 16B] = 0B;
  ivtmp.14_20 = ivtmp.14_9 + 24;
  if (ivtmp.14_20 != 24576)
    goto <bb 3>;
  else
    goto <bb 4>;


       reply	other threads:[~2011-12-24  3:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-28134-4@http.gcc.gnu.org/bugzilla/>
2011-12-24  3:16 ` pinskia at gcc dot gnu.org [this message]
2022-01-28 23:44 ` pinskia at gcc dot gnu.org
2006-06-22  3:30 [Bug tree-optimization/28134] New: " raeburn at raeburn dot org
2006-06-22  4:16 ` [Bug tree-optimization/28134] " raeburn at raeburn dot 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-28134-4-lEJMCXGPRr@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).