public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thopre01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/34503] Issues with constant/copy propagation implementation in gcse.c
Date: Fri, 24 Apr 2015 04:50:00 -0000	[thread overview]
Message-ID: <bug-34503-4-DIOp10GSGD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-34503-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34503

--- Comment #9 from Thomas Preud'homme <thopre01 at gcc dot gnu.org> ---
Author: thopre01
Date: Fri Apr 24 04:49:34 2015
New Revision: 222398

URL: https://gcc.gnu.org/viewcvs?rev=222398&root=gcc&view=rev
Log:
2015-04-24  Thomas Preud'homme  <thomas.preudhomme@arm.com>
            Steven Bosscher <steven@gcc.gnu.org>

    gcc/
    PR rtl-optimization/34503
    * 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/
    PR rtl-optimization/34503
    * gcc.target/arm/pr64616.c: New file.

Added:
    trunk/gcc/testsuite/gcc.target/arm/pr64616.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cprop.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2015-04-24  4:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-34503-4@http.gcc.gnu.org/bugzilla/>
2015-03-24 10:29 ` steven at gcc dot gnu.org
2015-04-24  4:50 ` thopre01 at gcc dot gnu.org [this message]
2007-12-17  8:17 [Bug rtl-optimization/34503] New: " steven at gcc dot gnu dot org
2007-12-17  8:20 ` [Bug rtl-optimization/34503] " steven at gcc dot gnu dot org
2007-12-17  8:22 ` steven at gcc dot gnu dot org
2007-12-17  8:31 ` steven at gcc dot gnu dot org
2007-12-17  8:38 ` steven at gcc dot gnu dot org
2007-12-17  8:41 ` steven at gcc dot gnu dot org
2007-12-17  8:42 ` steven at gcc dot gnu dot org
2008-05-24 14:32 ` steven at gcc dot gnu dot org
2010-02-12 22:00 ` steven at gcc dot gnu dot 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-34503-4-DIOp10GSGD@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).