[RFC] Add support for PPC Altivec registers in gcore

[Carlos Eduardo Seo]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Ulrich Weigand wrote:
>
> Completely removing all the fallbacks seems quite a bit of work;
> if you want to work on it that would certainly be welcome.
>
> However, I think it would be OK to start with having the gdbarch
> variable only contain the *extra* register sets, beyond the core
> and floating-point sets.
>
Ok. So, this would require removing the FILL_FPXREGSET ifdefs and all
the fill_fpxregset fallbacks. I think this is OK, but won't it break
anything in x86?
>
> If we do not have a collect_regset, we certainly do not want to
> write an note section containing uninitialized data.  The
> elfcore_write_ppc_vmx call needs to be inside the "if" block ...
Corrected.

Thanks,

- --
Carlos Eduardo Seo
Software Engineer
IBM Linux Technology Center
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJ54hqvq7Aov/qQARArXXAJ4z8a5f0YMzM2QxKX2QkuiJLTcGhgCbBsnS
NrH8jrngJzujytVbM/7wlXI=
=kR1E
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcore-altivec.diff
Type: text/x-patch
Size: 4467 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20071030/95b3e822/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcore-altivec.diff.sig
Type: application/octet-stream
Size: 65 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20071030/95b3e822/attachment.obj>