This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc-3.3 problem with reloading byte into address register on ColdFire

From: Richard Henderson <rth at redhat dot com>
To: Peter Barada <peter at baradas dot org>
Cc: wilson at tuliptree dot org, gcc at gcc dot gnu dot org
Date: Wed, 9 Jul 2003 11:57:11 -0700
Subject: Re: gcc-3.3 problem with reloading byte into address register on ColdFire
References: <20030702133736.DF05198B1D@baradas.org> <3F04E44E.3070208@tuliptree.org> <20030704210408.B747798B1D@baradas.org>

Why don't you save all the effort with secondary reloads etc
and just prohibit QImode values in ADDR_REGS entirely with
HARD_REGNO_MODE_OK?  Yes, it prohibits you using ADDR_REGS
for temporaries, but it is not clear to me that that gets
you better code.


r~

Follow-Ups:
- Re: gcc-3.3 problem with reloading byte into address register on ColdFire
  - From: Peter Barada

References:
- gcc-3.3 problem with reloading byte into address register on ColdFire
  - From: Peter Barada
- Re: gcc-3.3 problem with reloading byte into address register onColdFire
  - From: Jim Wilson
- Re: gcc-3.3 problem with reloading byte into address register onColdFire
  - From: Peter Barada

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]