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: rfc: unwinder, ppc-spe dual sized registers, and a patch...


Aldy Hernandez <aldyh at redhat dot com> writes:

> There is one heads up-- the ABI says the register pairs should be N and 
> N+1200 but this creates a huge hole in the unwinder tables, thus defeating
> the whole point, which was (well, to fix exception handling and...) 
> to save frame size.  I've set the pairs to N and N+113, unless someone
> has a huge objection.  This creates a bit of a confusion with the
> debugging info which is ABI compliant and has DW_OP_pieces of N and
> N+1200.  I'm willing to live with that.  Suggestions welcome.

This concerns me, because I (that is, CodeSourcery) have clients who
expect to be able to interoperate C++ code generated by GCC and by
their proprietary compiler, on the e500.  Can't you use a sparse array
or something?

zw


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