Audit support

[Steve Munroe]

Ulrich Drepper writes:

 > When do you think you can finally implement the audit code for ppc?
 > It's the last architecture missing the support.

The attached patch is (almost) complete for powerpc64 and if this is 
what you are looking for I will have the powerpc32 in daya or two.

However I do have a question about the symantics of the "framesize" 
parameter when it is none-negative and _dl_call_pltexit is called. In 
the general case we will need to copy the parameter save area of the 
calling frame to the _dl_runtime_profile frame for access by the target 
function. So I need to know exactly what the none-negative value of 
framesize represents.

If it is the total frame size of the target function that does not help 
as the parameter save area is allocated in th calling frame. I could 
compute the total size of the calling frame but this will include 
allocations for local variables and (non-volatile) register save areas, 
plus the maximum parameter save area of the functions called. This 
implies very large moves just to insure that the normally small 
parameter save area is included.

Is it posible for the framesize to be the actual target functions 
parameter save requirement?
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ppc64-audit-20050304.txt
URL: <http://sourceware.org/pipermail/libc-hacker/attachments/20050307/2e70cadc/attachment.txt>