This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] m68k: update various structures for arg pointer
- From: Gunther Nikl <gni at gecko dot de>
- To: Roman Zippel <zippel at linux-m68k dot org>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 10 Mar 2004 10:20:23 +0100
- Subject: Re: [PATCH] m68k: update various structures for arg pointer
- References: <Pine.LNX.4.58.0403100415210.7851@serv>
On Wed, Mar 10, 2004 at 04:28:28AM +0100, Roman Zippel wrote:
> ===================================================================
> RCS file: /cvsroot/gcc/gcc/gcc/config/m68k/m68k.c,v
> retrieving revision 1.128
> diff -u -r1.128 m68k.c
> --- gcc/config/m68k/m68k.c 17 Feb 2004 20:24:44 -0000 1.128
> +++ gcc/config/m68k/m68k.c 8 Mar 2004 20:00:23 -0000
> @@ -44,6 +44,18 @@
> #include "debug.h"
> #include "flags.h"
>
> +enum reg_class regno_reg_class[] =
Is there a reason that this has no const?
> Index: gcc/config/m68k/m68k.h
> ===================================================================
> RCS file: /cvsroot/gcc/gcc/gcc/config/m68k/m68k.h,v
> retrieving revision 1.109
> diff -u -r1.109 m68k.h
> --- gcc/config/m68k/m68k.h 15 Feb 2004 17:46:02 -0000 1.109
> +++ gcc/config/m68k/m68k.h 8 Mar 2004 20:00:24 -0000
> @@ -497,7 +500,18 @@
> #define CALL_USED_REGISTERS \
> {1, 1, 0, 0, 0, 0, 0, 0, \
> 1, 1, 0, 0, 0, 0, 0, 1, \
> - 1, 1, 0, 0, 0, 0, 0, 0 }
> + 1, 1, 0, 0, 0, 0, 0, 0, 1 }
> +
> +#define REG_ALLOC_ORDER \
> +{ /* d0/d1/a0/a1 */ \
> + 0, 1, 8, 9, \
> + /* d2-d7 */ \
> + 2, 3, 4, 5, 6, 7, \
> + /* a2-a7/arg */ \
> + 10, 11, 12, 13, 14, 15, 24, \
> + /* fp0-fp7 */ \
> + 16, 17, 18, 19, 20, 21, 22, 23\
> +}
Could you please explain why REG_ALLOC_ORDER is needed now? The
documenation didn't help me understanding its need here.
Gunther