This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: BIGGEST_ALIGNMENT on AIX 32-bit

From: Eric Botcazou <ebotcazou at adacore dot com>
To: David Edelsohn <dje at watson dot ibm dot com>
Cc: gcc at gcc dot gnu dot org
Date: Sat, 14 Jan 2006 18:01:54 +0100
Subject: Re: BIGGEST_ALIGNMENT on AIX 32-bit
References: <200601141431.09669.ebotcazou@adacore.com> <200601141603.48244.ebotcazou@adacore.com> <200601141611.k0EGBwD26800@makai.watson.ibm.com>

> 	Why isn't this bug an incorrect use of BIGGEST_ALIGNMENT somewhere
> in the compiler?

Because you must have BIGGEST_ALIGNMENT <= STACK_BOUNDARY (or 
PREFERRED_STACK_BOUNDARY) in order to be able to allocate objects with 
BIGGEST_ALIGNMENT on the stack.  Otherwise the offsets are not sufficiently 
rounded, even if the stack register is aligned on BIGGEST_ALIGNMENT on 
function entry.

-- 
Eric Botcazou

Follow-Ups:
- Re: BIGGEST_ALIGNMENT on AIX 32-bit
  - From: Andrew Pinski

References:
- BIGGEST_ALIGNMENT on AIX 32-bit
  - From: Eric Botcazou
- Re: BIGGEST_ALIGNMENT on AIX 32-bit
  - From: Eric Botcazou
- Re: BIGGEST_ALIGNMENT on AIX 32-bit
  - From: David Edelsohn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]