Re: Troubles building gcc-3.2.1 --target=m68k-linux

[Andreas Schwab <schwab@suse.de>]

Peter Barada <pbarada@mail.wm.sps.mot.com> writes:

|> >You need to have REG_OK_STRICT and !REG_OK_STRICT versions of the macro
|> >GO_IF_LEGITIMATE_ADDRESS.  See for instance the definition in the mips port.
|> >
|> >When strict is false, you can accept pseudo-regs where a reg is OK.
|> >When strict is true, you can't accept pseudo-regs where a reg is OK, because
|> >a pseudo-reg is actually a MEM refering to a stack-slot.
|> 
|> I was wondering about that, since I see that in the i386 version.
|> Eventually I'll include that in the new GO_IF_LEGITIMATE_ADDRESS for m68k.
|> 
|> What I'm *more* concerned (at the moment) is why as a macro
|> GO_IF_LEGITIMATE_ADDRESS works, but as a function it fails....

Because you only have one version, but all those macros ultimatively
depend on REG_OK_FOR_INDEX_P and REG_OK_FOR_BASE_P, and those differ
between REG_OK_STRICT and !REG_OK_STRICT.

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."