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

[Kevin Buettner <kevinb@redhat.com>]

On Nov 29,  6:37pm, Daniel Jacobowitz wrote:

> On Thu, Nov 29, 2001 at 04:12:29PM -0700, Kevin Buettner wrote:
> > > My still-unsubmitted cross-core patches for PowerPC remove
> > > core-regset.o also, and very unpleasantly turn ppc-linux-nat.c into a
> > > target-dependant rather than native-dependant file, so that we can grub
> > > through the gregsets by hand.  If you've got a better idea I'd love to
> > > hear it :) It will be made somewhat easier by the destruction of
> > > regmap[].
> > 
> > I haven't seen your patches, but I imagine you have a table of
> > constants or some such that represent offsets and sizes of members in
> > the regsets?  (I.e, something similar to what I did for SVR4 shared
> > library offsets.) If that's the approach, then the only real problem I
> > have with it is accurately generating (and maintaining) the tables. 
> > The SVR4 shared library tables are compact enough to easily generate
> > by hand.  The regset data is quite a lot larger and I would think
> > you'd want to generate this data through more automatic means.  (I.e,
> > via a program that you'd compile and and then run on the target.)
> 
> Nothing that abstracted.  I copy the necessary type definitions and
> constants from target headers; they are "relatively" guaranteed never
> to change.  It's a mess.

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?