This is the mail archive of the gcc-patches@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]

Re: altivec patches


> Date: Wed, 7 Nov 2001 11:41:11 -0800
> From: Richard Henderson <rth@redhat.com>
> Cc: aldyh@redhat.com, gcc-patches@gcc.gnu.org
> Mail-Followup-To: Richard Henderson <rth@redhat.com>,
> 	Geoff Keating <geoffk@redhat.com>, aldyh@redhat.com,
> 	gcc-patches@gcc.gnu.org
> Content-Disposition: inline
> User-Agent: Mutt/1.2.5i
> 
> On Wed, Nov 07, 2001 at 02:49:15AM -0800, Geoff Keating wrote:
> > Here I was talking about BIGGEST_ALIGNMENT only.  Changing
> > STACK_BOUNDARY is of course an ABI change.
> 
> Well, there is
> 
>   struct {
>     int x __attribute__((aligned));
>     int y;
>   };
> 
> to name one place that BIGGEST_ALIGNMENT affects the ABI.
> I suspect there are other places as well.

Hmmm.  Well, we'll see.

> > Can we really change the EH library interface like this?  Even in the
> > presence of a glibc compatibility layer to support pre-gcc3.0 C++
> > binaries?
> 
> Pre gcc 3.0, we don't support altivec, so we don't have to worry 
> about this.

Yes, but that's the question:  Can this be changed even for
non-altivec compilations?

-- 
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>


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