more m68k breakage on m68k-linux

[Gunther Nikl]

Hello Bernado!

On Mon, Mar 08, 2004 at 10:38:03PM +0100, Bernardo Innocenti wrote:
> Gunther Nikl wrote:
> >On Sun, Mar 07, 2004 at 04:05:50PM +0100, Bernardo Innocenti wrote:
> >
> >>Roman Zippel wrote:
> >>
> >>>Does your patch look very different from the one below?
> >>>That's the one I'm testing for m68k-linux right now.
> >>
> >>It's similar, but I didn't notice REGNO_REG_CLASS also needed fiddling,
> >>so your patch is superior.
> >
> >  Why are so many changes required to fix the breakage caused by adding
> >  argptr?
> 
> Because the target configuration infrastructure used by GCC is a hell
> ofpreprocessor macros with very weak consistency checking? :-)

  No, that wasn't my real question ;-) I thought that just adding argptr
  to FIXED_REGISTERS+CALL_USED_REGISTERS would be enough. But the patch
  adds REG_ALLOC_ORDER and modifies REG_CLASS_CONTENTS+REGNO_REG_CLASS.
  I checked the documenation but it wasn't that helpful regarding
  REG_ALLOC_ORDER. Why is that one now needed?
  BTW, the patch should be posted quickly because  according to
  http://gcc.gnu.org/ml/gcc-patches/2004-03/msg00513.html 3.4.0 is
  scheduled for its final code freeze soon. IMHO, this patch must be
  in 3.4.0.

  Thank you,
  Gunther