public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/40730] redundant memory load
Date: Mon, 13 Jul 2009 09:51:00 -0000	[thread overview]
Message-ID: <20090713095047.1295.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40730-17659@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rguenth at gcc dot gnu dot org  2009-07-13 09:50 -------
-fgcse-las should do the trick.  Note that PRE would do this kind of
optimization on the tree-level, but it is disabled with -Os (so is gcse).

<bb 2>:
  D.1614_2 = p2_1(D)->front;
  p1_3(D)->head = D.1614_2;
  goto <bb 4>;

<bb 3>:
  D.1616_8 = D.1615_4->next;
  p1_3(D)->head = D.1616_8;

<bb 4>:
  D.1615_4 = p1_3(D)->head;


-- 


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


  parent reply	other threads:[~2009-07-13  9:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  8:57 [Bug target/40730] New: " carrot at google dot com
2009-07-13  8:58 ` [Bug target/40730] " carrot at google dot com
2009-07-13  9:51 ` rguenth at gcc dot gnu dot org [this message]
2009-07-13 10:10 ` steven at gcc dot gnu dot org
2009-07-14  9:14 ` carrot at google dot com
2009-07-14  9:18 ` steven at gcc dot gnu dot org
2009-07-14  9:20 ` steven at gcc dot gnu dot org
2009-07-15  8:07 ` carrot at google dot com
2009-07-15  9:47 ` steven at gcc dot gnu dot org
2010-01-08  9:34 ` steven at gcc dot gnu dot org
2010-01-11  6:47 ` carrot at google dot com
2010-01-11  8:23 ` stevenb dot gcc at gmail dot com
2010-01-11  8:56 ` carrot at google dot com
     [not found] <bug-40730-4@http.gcc.gnu.org/bugzilla/>
2023-05-15  0:10 ` pinskia at gcc dot gnu.org
2023-05-15  0:24 ` 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=20090713095047.1295.qmail@sourceware.org \
    --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).