public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jiangning.liu at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50272] A case that PRE optimization hurts performance
Date: Fri, 02 Sep 2011 05:12:00 -0000	[thread overview]
Message-ID: <bug-50272-4-U6Jf8zF76f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50272-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Jiangning Liu <jiangning.liu at arm dot com> 2011-09-02 05:11:38 UTC ---
Richard gave some analysis at http://gcc.gnu.org/ml/gcc/2011-08/msg00037.html


  reply	other threads:[~2011-09-02  5:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02  5:08 [Bug c/50272] New: " jiangning.liu at arm dot com
2011-09-02  5:12 ` jiangning.liu at arm dot com [this message]
2011-09-02  6:29 ` [Bug tree-optimization/50272] " pinskia at gcc dot gnu.org
2011-09-02  9:28 ` rguenth at gcc dot gnu.org
2011-09-08 20:41 ` hp at gcc dot gnu.org
2012-03-29 17:56 ` vhaisman at gmail dot com
2012-03-30  3:48 ` liujiangning at gcc dot gnu.org
2021-07-26 20:54 ` 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-50272-4-U6Jf8zF76f@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).