public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64539] [5 regression] cprop_hardreg does not respect clobbers in C_I_F_U
Date: Fri, 09 Jan 2015 18:55:00 -0000	[thread overview]
Message-ID: <bug-64539-4-JOhcvXPaJx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64539-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from vries at gcc dot gnu.org ---
Author: vries
Date: Fri Jan  9 18:54:20 2015
New Revision: 219400

URL: https://gcc.gnu.org/viewcvs?rev=219400&root=gcc&view=rev
Log:
Handle CALL_INSN_FUNCTION_USAGE clobbers in regcprop.c

2015-01-09  Tom de Vries  <tom@codesourcery.com>

    PR rtl-optimization/64539
    * regcprop.c (kill_clobbered_values): Factor out of ...
    (copyprop_hardreg_forward_1): ... here.  Use kill_clobbered_values
    instead of note_stores with kill_clobbered_value.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/regcprop.c


  parent reply	other threads:[~2015-01-09 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 14:16 [Bug rtl-optimization/64539] New: " vries at gcc dot gnu.org
2015-01-08 14:23 ` [Bug rtl-optimization/64539] " vries at gcc dot gnu.org
2015-01-08 17:38 ` vries at gcc dot gnu.org
2015-01-09  8:32 ` vries at gcc dot gnu.org
2015-01-09  8:38 ` vries at gcc dot gnu.org
2015-01-09  8:49 ` terry.guo at arm dot com
2015-01-09 10:58 ` vries at gcc dot gnu.org
2015-01-09 11:20 ` rguenth at gcc dot gnu.org
2015-01-09 18:55 ` vries at gcc dot gnu.org [this message]
2015-01-09 19:02 ` vries at gcc dot gnu.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-64539-4-JOhcvXPaJx@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).