This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bug in gcc CVS HEAD from a few days ago with alloca and stack alignment
- To: David Edelsohn <dje at watson dot ibm dot com>,khendricks at ivey dot uwo dot ca
- Subject: Re: Bug in gcc CVS HEAD from a few days ago with alloca and stack alignment
- From: Kevin B. Hendricks <khendricks at ivey dot uwo dot ca>
- Date: Sat, 10 Feb 2001 22:50:48 -0500
- Cc: java at gcc dot gnu dot org,gcc at gcc dot gnu dot org
- References: <200102110033.TAA37292@mal-ach.watson.ibm.com>
- Reply-To: khendricks at ivey dot uwo dot ca
Hi David,
Thanks!
I changed STACK_BOUNDARY to 128 and rebuilt the entire gcc and now everything
has started working including the gcj closure code and the gij interpreter.
Will you please commit a proper fix? Franz's mail machine bounced my last
mail so I don't think he knows about this problem.
Take care,
Kevin
On Saturday 10 February 2001 19:33, David Edelsohn wrote:
> This is probably caused by the following definition in
> config/rs6000/sysv4.h:
>
> /* Alignment in bits of the stack boundary. Note, in order to allow
building
> one set of libraries with -mno-eabi instead of eabi libraries and
non-eabi
> versions, just use 64 as the stack boundary. */
> #undef STACK_BOUNDARY
> #define STACK_BOUNDARY 64
>
> /* Real stack boundary as mandated by the appropriate ABI. */
> #define ABI_STACK_BOUNDARY ((TARGET_EABI) ? 64 : 128)
>
>
> So it looks to me that this is some incorrect accomodation made
> for eABI, i.e., someone trying to use the sysv4 configuration for eABI
> instead of creating a real cross-compiler.
>
> I do not know the history of this decision.
>
> David