From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Zhenqiang Chen <zhenqiang.chen@linaro.org>
Cc: gcc-patches@gcc.gnu.org, Martin Jambor <mjambor@suse.cz>
Subject: Re: [PATCH] Enhance shrink-wrap
Date: Thu, 06 Jun 2013 12:44:00 -0000 [thread overview]
Message-ID: <CABu31nMr6BDZXmEKjHk3XdXATcb6TyMJXwnG991LtQ_LSQb2eg@mail.gmail.com> (raw)
In-Reply-To: <CACgzC7Dyrc4Zc=WDKy=m03Wwp3hmrgD315b5vRuV9_gO_4MA-A@mail.gmail.com>
On Thu, Jun 6, 2013 at 11:55 AM, Zhenqiang Chen wrote:
> The patch enhance prepare_shrink_wrap by doing copyprop for the entry
> block. This exposes more opportunities for shrink-wrapping. These
> kinds of copies often occur when incoming argument registers are moved
> to call-saved registers because their values are live across one or
> more calls during the function.
Hello,
This was discussed before, see the thread surrounding:
http://gcc.gnu.org/ml/gcc-patches/2013-04/msg01455.html
This is also http://gcc.gnu.org/PR10474
Ciao!
Steven
prev parent reply other threads:[~2013-06-06 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 9:55 Zhenqiang Chen
2013-06-06 12:44 ` Steven Bosscher [this message]
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=CABu31nMr6BDZXmEKjHk3XdXATcb6TyMJXwnG991LtQ_LSQb2eg@mail.gmail.com \
--to=stevenb.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mjambor@suse.cz \
--cc=zhenqiang.chen@linaro.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).