public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: "Thomas Preud'homme" <thomas.preudhomme@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH, GCC, stage1] Fallback to copy-prop if constant-prop not possible
Date: Mon, 16 Feb 2015 12:06:00 -0000	[thread overview]
Message-ID: <CABu31nP6qZmfUugRC=kM-DgDzw8fVwMD4+Oh3hR7gOQmkC2rFg@mail.gmail.com> (raw)
In-Reply-To: <000501d049d3$079385a0$16ba90e0$@arm.com>

On Mon, Feb 16, 2015 at 11:26 AM, Thomas Preud'homme
<thomas.preudhomme@arm.com> wrote:
> Hi,
>
> The RTL cprop pass in GCC operates by doing a local constant/copy propagation first and then a global one. In the local one, if a constant cannot be propagated (eg. due to constraints of the destination instruction) a copy propagation is done instead. However, at the global level copy propagation is only tried if no constant can be propagated, ie. if a constant can be propagated but the constraints of the destination instruction forbids it, no copy propagation will be tried. This patch fixes this issue. This solves the redundant ldr problem in GCC32RM-439.
>

This would address https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34503#c4

I'll have a look at the patch tonight.

Ciao!
Seven

  parent reply	other threads:[~2015-02-16 12:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 10:26 Thomas Preud'homme
2015-02-16 10:54 ` Richard Biener
2015-02-16 12:06 ` Steven Bosscher [this message]
2015-02-16 20:20 ` Steven Bosscher
2015-02-17  2:51   ` Thomas Preud'homme
2015-03-04  8:52     ` Thomas Preud'homme
2015-03-20  7:55     ` Steven Bosscher
2015-03-20  8:36       ` Thomas Preud'homme
2015-03-20 10:27         ` Thomas Preud'homme
2015-03-20 12:14           ` Steven Bosscher
2015-03-23 11:01             ` Thomas Preud'homme
2015-03-23 11:57               ` Steven Bosscher
2015-03-30  4:58               ` Thomas Preud'homme
2015-04-13 12:47 ` Jeff Law
2015-04-14  8:00   ` Thomas Preud'homme
2015-04-16  8:44   ` Thomas Preud'homme
2015-04-23  9:15     ` Steven Bosscher
2015-04-24  2:59     ` Jeff Law
2015-04-24  3:11       ` Thomas Preud'homme
2015-04-24  3:15         ` Jeff Law
2015-04-24  4:53           ` Thomas Preud'homme
2015-04-30  7:43             ` Bin.Cheng

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='CABu31nP6qZmfUugRC=kM-DgDzw8fVwMD4+Oh3hR7gOQmkC2rFg@mail.gmail.com' \
    --to=stevenb.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    --cc=thomas.preudhomme@arm.com \
    /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).