This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Altivec + 16 byte alignment
- From: David Edelsohn <dje at watson dot ibm dot com>
- To: Geoff Keating <geoffk at geoffk dot org>
- Cc: kenner at vlsi1 dot ultra dot nyu dot edu, gcc at gcc dot gnu dot org
- Date: Tue, 11 Feb 2003 14:38:45 -0500
- Subject: Re: Altivec + 16 byte alignment
>>>>> Geoff Keating writes:
Geoff> In the abstract, you compare with MAX_OFILE_BOUNDARY. You can align
Geoff> the stack to any value you like, but you can't do better than
Geoff> MAX_OFILE_BOUNDARY in the object file.
I think part of the confusion is this depends on the type of
storage. For an automatic variable on the stack, MAX_OFILE_ALIGNMENT is
irrelevant. For a global or static variable allocated in the data or bss
segment, MAX_OFILE_ALIGNMENT describes the functionality of the
link-editor pre-allocating storage in the process address space.
David