|
From: Julian S. <js...@ac...> - 2004-10-14 10:49:00
|
> > > arch-specifics in tools whenever possible: E.g. in cachegrind (and > > > calltree also), there is the MMX/SSE stuff. Perhaps some functions > > > could be added providing additional high level properties for UOps like > > > if it is accessing memory and so on. Prove of concept would be a > > > cachegrind with same source for PowerPC, x86 and x86_64. > > > > I think that sort of thing comes under the heading of reworking UCode > > for better platform independence which I believe Julian is working on? > > Yes, but reworking UCode is quite difficult to get it right. But this seems > to be a worthwhile short-term goal. Perhaps here also, a library between > Valgrind and the tool (as proposed above) is the best for this kind of > thing. An architecture-neutral IR is definitely under development and it will allow you to avoid arch-specifics in tools -- that is one of the design goals. For the cache profilers, all you want to see is (1) all load and store insns, including data sizes and addresses, and (2) where the boundaries between original client instructions are. I'm sure this will be possible with no great problems. J |