Subject: Re: Altivec registers
To: matthew green <>
From: Andrew Cagney <>
List: port-powerpc
Date: 12/02/2001 10:53:18
>  So the first step is to define an interface for getting at "extra"
>    registers such as Altivec and SSE - a PT_GETOTHERREGS would probably
>    work, but will lose as soon as we get Altivec2 registers or something
>    - and then do a little back-end glue in the PowerPC process_machdep.c
>    to recognize it.


> couldn't we use the "int data" param of ptrace(2) to allow the new
> PT_[GS]ETOTHERREGS to have an additional argument?  that would allow
> fairly extensive expansion :-)

``int data', what ``int data'' parameter?  Oh that one.  Hmmm, interesting.

Same problem occures with core.  The convention is .reg (gen) & .reg2 
(fp) but after that all bets appear to be off.  Is there a standard


(There is apparently also a (i386? XXX kernel? specific) .reg-xfp 
section kicking around but I have no idea where that came from or if 
anything even uses it.)