|
From: Geoff S. <gs...@us...> - 2006-02-24 09:03:37
|
Julian Seward <js...@ac...> wrote on 02/23/2006 10:07:42 AM: > > > How have you used it? > > > Nick > > > > We took the output trace and fed it into a tool that displays pipeline > > stalls for the Power5 processor. Recently, we have been working on > > improving the performance of a few key routines in glibc. We're currently > > looking at a few functions in the math libraries. > > So the output format of itrace is the same as the input format of your > pipeline tool? (Is the latter open-source?) Not quite, but we wrote a small adapter to convert itrace's straightforward format to the format the pipeline tool wanted. The pipeline tool is not open-source, but it is freely available (as a binary) on IBM's alphaworks site -- it's called IBM Performance Simulator. It's available for a couple processors. For my part, this is just one possible use for itrace, and not even a particularly interesting one (to me, anyway). I am much more interested in code coverage -- this looks like a tractable way to get coverage on optimized code, which is something gcov can't do. Of course, the kinds of projects that need object-level coverage are probably not considering Linux (yet). |