summaryrefslogtreecommitdiff
path: root/gcc/ira.c
diff options
context:
space:
mode:
authorbstarynk <bstarynk@138bc75d-0d04-0410-961f-82ee72b054a4>2009-09-05 13:03:46 +0000
committerbstarynk <bstarynk@138bc75d-0d04-0410-961f-82ee72b054a4>2009-09-05 13:03:46 +0000
commitd480913686c7452f216d96d0bcd0f494cfc747a8 (patch)
tree15a68521afc8fe5f85d09ad5ad2c4f06148ab9d2 /gcc/ira.c
parented56287f7fc87c1ebacb100627f37ddafbc8b6a6 (diff)
downloadgcc-d480913686c7452f216d96d0bcd0f494cfc747a8.tar.gz
2009-09-05 Basile Starynkevitch <basile@starynkevitch.net>
MELT branch merged with trunk rev 151445 git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/melt-branch@151449 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/ira.c')
-rw-r--r--gcc/ira.c14
1 files changed, 13 insertions, 1 deletions
diff --git a/gcc/ira.c b/gcc/ira.c
index b9b10dc9d3c..b960f769534 100644
--- a/gcc/ira.c
+++ b/gcc/ira.c
@@ -2384,9 +2384,21 @@ update_equiv_regs (void)
/* We only handle the case of a pseudo register being set
once, or always to the same value. */
+ /* ??? The mn10200 port breaks if we add equivalences for
+ values that need an ADDRESS_REGS register and set them equivalent
+ to a MEM of a pseudo. The actual problem is in the over-conservative
+ handling of INPADDR_ADDRESS / INPUT_ADDRESS / INPUT triples in
+ calculate_needs, but we traditionally work around this problem
+ here by rejecting equivalences when the destination is in a register
+ that's likely spilled. This is fragile, of course, since the
+ preferred class of a pseudo depends on all instructions that set
+ or use it. */
+
if (!REG_P (dest)
|| (regno = REGNO (dest)) < FIRST_PSEUDO_REGISTER
- || reg_equiv[regno].init_insns == const0_rtx)
+ || reg_equiv[regno].init_insns == const0_rtx
+ || (CLASS_LIKELY_SPILLED_P (reg_preferred_class (regno))
+ && MEM_P (src) && ! reg_equiv[regno].is_arg_equivalence))
{
/* This might be setting a SUBREG of a pseudo, a pseudo that is
also set somewhere else to a constant. */