public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernds at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/42502] [4.4/4.5/4.6 Regression] Bad register allocation in a very simple code Date: Fri, 04 Jun 2010 12:44:00 -0000 [thread overview] Message-ID: <20100604124429.21384.qmail@sourceware.org> (raw) In-Reply-To: <bug-42502-17572@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from bernds at gcc dot gnu dot org 2010-06-04 12:44 ------- Subject: Bug 42502 Author: bernds Date: Fri Jun 4 12:44:01 2010 New Revision: 160260 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=160260 Log: PR rtl-optimization/39871 PR rtl-optimization/40615 PR rtl-optimization/42500 PR rtl-optimization/42502 * ira.c (init_reg_equiv_memory_loc: New function. (ira): Call it twice. * reload.h (calculate_elim_costs_all_insns): Declare. * ira-costs.c: Include "reload.h". (regno_equiv_gains): New static variable. (init_costs): Allocate it. (finish_costs): Free it. (ira_costs): Call calculate_elim_costs_all_insns. (find_costs_and_classes): Take estimated elimination costs into account. (ira_adjust_equiv_reg_cost): New function. * ira.h (ira_adjust_equiv_reg_cost): Declare it. * reload1.c (init_eliminable_invariants, free_reg_equiv, elimination_costs_in_insn, note_reg_elim_costly): New static functions. (elim_bb): New static variable. (reload): Move code out of here into init_eliminable_invariants and free_reg_equiv. Call them. (calculate_elim_costs_all_insns): New function. (eliminate_regs_1): Declare. Add extra arg FOR_COSTS; all callers changed. If FOR_COSTS is true, don't call alter_reg, but call note_reg_elim_costly if we turned a valid memory address into an invalid one. * Makefile.in (ira-costs.o): Depend on reload.h. testsuite/ PR rtl-optimization/39871 PR rtl-optimization/40615 PR rtl-optimization/42500 PR rtl-optimization/42502 * gcc.target/arm/eliminate.c: New test. Added: trunk/gcc/testsuite/gcc.target/arm/eliminate.c Modified: trunk/gcc/ChangeLog trunk/gcc/Makefile.in trunk/gcc/ira-costs.c trunk/gcc/ira.c trunk/gcc/ira.h trunk/gcc/reload.h trunk/gcc/reload1.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42502
next prev parent reply other threads:[~2010-06-04 12:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-25 13:10 [Bug rtl-optimization/42502] New: " sliao at google dot com 2009-12-31 15:28 ` [Bug rtl-optimization/42502] " rguenth at gcc dot gnu dot org 2010-01-07 13:28 ` sliao at google dot com 2010-01-12 9:36 ` ramana at gcc dot gnu dot org 2010-02-08 12:49 ` steven at gcc dot gnu dot org 2010-02-10 11:01 ` [Bug rtl-optimization/42502] [4.4/4.5 Regression] " steven at gcc dot gnu dot org 2010-02-10 11:47 ` rguenth at gcc dot gnu dot org 2010-02-17 17:21 ` mmitchel at gcc dot gnu dot org 2010-02-25 16:01 ` cltang at pllab dot cs dot nthu dot edu dot tw 2010-03-15 23:44 ` bernds at codesourcery dot com 2010-04-30 8:56 ` [Bug rtl-optimization/42502] [4.4/4.5/4.6 " jakub at gcc dot gnu dot org 2010-06-04 12:44 ` bernds at gcc dot gnu dot org [this message] [not found] <bug-42502-4@http.gcc.gnu.org/bugzilla/> 2010-10-01 11:57 ` jakub 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=20100604124429.21384.qmail@sourceware.org \ --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: linkBe 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).