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

Andreas Schwab schwab@suse.de
Mon Jul 7 09:19:00 GMT 2003


Peter Barada <peter@baradas.org> writes:

|> >Looking at a m68k manual, I see that no member of the m68k family
|> >supports QImode moves to/from address registers.  This isn't a Coldfire
|> >specific problem.  If you look at output_move_qimode, it always uses a
|> >word-sized (HImode) move if the source or destination is an address
|> >register.  So my initial analysis was wrong.
|> 
|> According to the 68000 Programmers Reference Manual, move.b could use
|> an address register as a source operand, bot not a destination
|> operand.

There is a footnote saying "For byte size operation, address register
direct is not allowed."  Experimentation confirms that.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



More information about the Gcc mailing list