This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Mudflap based memprofiler


Hello,
I am working on a memory profiler project. It based on existing mudflap
extension of GCC. During compilation calls to library functions are
inserted before places of interest (like access to arrays and so on). In
current implementation these library functions just dump info into a file
that is later analyzed by a special program. However it's easy to imagine
that visualization/analysis can occur during program execution.
It's not intended to be a general-purpose profiler tool, like gprof or
valgrind, instead it is focused on analyzing memory access patterns.
Such analysis may help with finding poor code (like indexing arrays by
columns) and suggest code optimization (like adding additional thread of
execution on smp for paticular piece of code)

Screenshot
http://z888.narod.ru/sshot12.png

For curious, here is c program source that which memory access patterns
you see on screenshot:
http://z888.narod.ru/a1.c

Alex Iliasov


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]