|
From: Josef W. <Jos...@gm...> - 2006-08-28 17:07:31
|
On Monday 28 August 2006 15:03, Bryan Meredith wrote: > I agree that would be the best solution but how does one work out the > compiler, given the IR (or is it buried in the debug info somewhere). If there is full debug information, you should be able to extract everything you need (e.g. return type of a function). AFAIK, Valgrind currently does parse symbol tables and line debug info, but not much more. It would be cool to have a debug info parser for further info like type and variable name available for tools (for DWARF format). Regarding push/pop vs. mov(sp): It can be that this is an architecture optimization issue, and does change depending on command line options; ie. not really depending on the compiler itself - but perhaps the defaults for command line options have changed. Josef |