From: Steven Bosscher <stevenb.gcc@gmail.com>
To: "Thomas Preud'homme" <thomas.preudhomme@arm.com>
Cc: Jeff Law <law@redhat.com>, 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: Thu, 23 Apr 2015 09:15:00 -0000 [thread overview]
Message-ID: <CABu31nPCXb631xgRbDKmbo4otuE=xZ-mk4p5y5p7BXJzo9g4_w@mail.gmail.com> (raw)
In-Reply-To: <000001d07821$6fb82f60$4f288e20$@arm.com>
On Thu, Apr 16, 2015 at 10:43 AM, Thomas Preud'homme wrote:
> 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.
I wouldn't usually approve patches I've coded bits in myself. But this
post is now 7 days old and it's Thomas' patch for 99%, so...
OK for trunk.
Can you please put steven at gcc.gnu.org for my e-mail address in the
ChangeLog entry?
Ciao!
Steven
next prev parent reply other threads:[~2015-04-23 9:15 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 [this message]
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='CABu31nPCXb631xgRbDKmbo4otuE=xZ-mk4p5y5p7BXJzo9g4_w@mail.gmail.com' \
--to=stevenb.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--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).