[RFA] W.I.P. AltiVec ppc registers support.

[Daniel Jacobowitz]

On Thu, Nov 29, 2001 at 07:17:56PM -0500, Andrew Cagney wrote:
> >>How does the "cross" part of it work then?  Won't the sizes of the
> >>fundamental types, struct alignment, etc. change depending upon
> >>which host you compile it on?
> >
> >
> >How does it work?  Badly.
> >
> >The types look like this right now:
> >
> >+typedef unsigned char elf_greg_t[4];
> >+typedef unsigned char elf_fpreg_t[8];
> >+typedef struct {
> >+  unsigned char u[16];
> >+} __attribute((aligned(16))) __uint128_t;
> >+/* Altivec registers */
> >+typedef __uint128_t elf_vrreg_t;
> 
> Hmm, Kevin did have good reason to be concerned.  That is wrong. 
> Mechanisms similar to shlib et.al. should be used.

What is wrong with it?

I agree that it is messy, but it is completely correct.  I know of no
platform with 8-bit bytes stupid enough to do this any way other than
the way I intend.

> BTW, where did this buffer layout come from?

Eh?  It's the layout of a ppc/linux elf_gregset_t.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer