This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: gcc pdp11 port
- To: lars brinkhoff <lars at nocrew dot org>
- Subject: Re: gcc pdp11 port
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Thu, 18 May 2000 11:14:46 -0600
- cc: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>, gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <85wvks3u8g.fsf@junk.nocrew.org>you write:
> "Joseph S. Myers" <jsm28@cam.ac.uk> writes:
> > I know the following need doing with the port, but haven't had time to
> > work on them:
> > * May not compile in current snapshots (needs PREFERRED_STACK_BOUNDARY,
> > easy to fix).
>
> Something like this?
>
> --- gcc-cvs/gcc/config/pdp11/pdp11.h Mon May 1 19:31:30 2000
> +++ gcc-cvs-pdp11/gcc/config/pdp11/pdp11.h Thu May 18 14:18:17 2000
> @@ -193,6 +193,13 @@
> /* Allocation boundary (in *bits*) for storing arguments in argument list.
> */
> #define PARM_BOUNDARY 16
>
> +/* Boundary (in *bits*) on which stack pointer should be aligned. */
> +#define STACK_BOUNDARY 16
> +
> +/* Boundary (in *bits*) on which the stack pointer preferrs to be
> + aligned; the compiler cannot rely on having this alignment. */
> +#define PREFERRED_STACK_BOUNDARY 16
> +
> /* Allocation boundary (in *bits*) for the code of a function. */
> #define FUNCTION_BOUNDARY 16
I do not think you need PREFERRED_STACK_BOUNDARY if it would be the same
as STACK_BOUNDARY.
jeff