From: Jeff Law <law@redhat.com>
To: "Thomas Preud'homme" <thomas.preudhomme@arm.com>,
Steven Bosscher <stevenb.gcc@gmail.com>,
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: Fri, 24 Apr 2015 02:59:00 -0000 [thread overview]
Message-ID: <5539B177.8020705@redhat.com> (raw)
In-Reply-To: <000001d07821$6fb82f60$4f288e20$@arm.com>
On 04/16/2015 02:43 AM, Thomas Preud'homme wrote:
>> From: Jeff Law [mailto:law@redhat.com]
>> Sent: Monday, April 13, 2015 8:48 PM
>>
>> I know there were several followups between Steven and yourself.
>> With
>> stage1 now open, can you post a final version and do a final
>> bootstrap/test with it?
>
> Here is what came out of our discussion with Steven:
>
> 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.
>
> ChangeLog entries are as follows:
>
> *** gcc/ChangeLog ***
>
> 2015-04-15 Thomas Preud'homme <thomas.preudhomme@arm.com>
> Steven Bosscher <stevenb.gcc@gmail.com>
>
> * cprop.c (cprop_reg_p): New.
> (hash_scan_set): Use above function to check if register can be
> propagated.
> (find_avail_set): Return up to two sets, one whose source is
> a register and one whose source is a constant. Sets are returned in
> an array passed as parameter rather than as a return value.
> (cprop_insn): Use a do while loop rather than a goto. Try each of the
> sets returned by find_avail_set, starting with the one whose source is
> a constant. Use cprop_reg_p to check if register can be propagated.
> (do_local_cprop): Use cprop_reg_p to check if register can be
> propagated.
> (implicit_set_cond_p): Likewise.
>
> *** gcc/testsuite/ChangeLog ***
>
> 2015-04-15 Thomas Preud'homme <thomas.preudhomme@arm.com>
> Steven Bosscher <stevenb.gcc@gmail.com>
>
> * gcc.target/arm/pr64616.c: New file.
>
>
> And the patch is:
>
>
> diff --git a/gcc/cprop.c b/gcc/cprop.c
> index c9fb2fc..78541cf 100644
> --- a/gcc/cprop.c
> +++ b/gcc/cprop.c
> @@ -285,6 +285,15 @@ cprop_constant_p (const_rtx x)
> return CONSTANT_P (x) && (GET_CODE (x) != CONST || shared_const_p (x));
> }
>
> +/* Determine whether the rtx X should be treated as a register that can
> + be propagated. Any pseudo-register is fine. */
> +
> +static bool
> +cprop_reg_p (const_rtx x)
> +{
> + return REG_P (x) && !HARD_REGISTER_P (x);
> +}
How about instead this move to a more visible location (perhaps a macro
in regs.h or an inline function). Then as a followup, change the
various places that have this sequence to use that common definition
that exist outside of cprop.c.
> @@ -1191,7 +1192,7 @@ do_local_cprop (rtx x, rtx_insn *insn)
> /* Rule out USE instructions and ASM statements as we don't want to
> change the hard registers mentioned. */
> if (REG_P (x)
> - && (REGNO (x) >= FIRST_PSEUDO_REGISTER
> + && (cprop_reg_p (x)
> || (GET_CODE (PATTERN (insn)) != USE
> && asm_noperands (PATTERN (insn)) < 0)))
Isn't the REG_P test now redundant?
OK for the trunk with those changes.
jeff
next prev parent reply other threads:[~2015-04-24 2:59 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
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 [this message]
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=5539B177.8020705@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=stevenb.gcc@gmail.com \
--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).