Cachegrind's cache mode is not very general and I wonder if it makes sense to use it on Quark to get at least approximate results on an application's cache performance. The Quark's cache is integrated (both instruction and data) single level 16kB size with16B line.
My best bet that is to run $ valgrind --tool=cachegrind --I1=32,2,16 --D1=32,2,16 --LL=16384,2,16 prog and look at LL statistics. Sure it's not the real thing but seems the closest I can get. But maybe I miss something and there is some better way... Any suggestions welcome, Krzysztof
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
