public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49801] df_live_verify_transfer_functions fails with to use of CC_REGNUM and checking enabled in rx backend
Date: Mon, 10 Oct 2011 13:31:00 -0000	[thread overview]
Message-ID: <bug-49801-4-STcePohR7H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49801-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49801

--- Comment #9 from Nick Clifton <nickc at gcc dot gnu.org> 2011-10-10 13:31:10 UTC ---
Author: nickc
Date: Mon Oct 10 13:31:03 2011
New Revision: 179749

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=179749
Log:
    PR middle-end/49801
    * compare-elim.c (find_comparisons_in_bb): Use df_get_live_in and
    df_get_live_out instead of accessing the bitmaps directly.
    (execute_compare_elim_after_reload): Remove calls to df_set_flags,
    df_live_add_problem and df_analyze.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/compare-elim.c


  parent reply	other threads:[~2011-10-10 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21  8:47 [Bug c/49801] New: " Paulo.Matos at csr dot com
2011-07-21  9:03 ` [Bug c/49801] " Paulo.Matos at csr dot com
2011-08-11  8:45 ` [Bug middle-end/49801] " Paulo.Matos at csr dot com
2011-10-04  9:09 ` nickc at redhat dot com
2011-10-05 11:08 ` Paulo.Matos at csr dot com
2011-10-06 14:22 ` nickc at redhat dot com
2011-10-06 14:25 ` nickc at redhat dot com
2011-10-06 21:37 ` rth at gcc dot gnu.org
2011-10-06 21:59 ` rth at gcc dot gnu.org
2011-10-07  7:35 ` bonzini at gnu dot org
2011-10-10 13:31 ` nickc at gcc dot gnu.org [this message]
2011-10-10 13:35 ` nickc at redhat dot com
2011-10-11  7:50 ` nickc at gcc dot gnu.org
2011-10-17 15:28 ` Paulo.Matos at csr dot com
2012-01-20  9:01 ` bonzini at 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-49801-4-STcePohR7H@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).