https://bugs.kde.org/show_bug.cgi?id=203380
Edd Barrett <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Edd Barrett <[email protected]> --- Hi. Julian's latest patch still applies and works on today's valgrind. Thanks for this Julian. I was able to cachegrind our JIT and assign names to our dynamically compiled code ranges and view them in kcachegrind. Before, the JITted code would be clumped into the `???` record in the output file, which was rendered as a `(unknown)` in kcachegrind. (I spoke to a few people in #valgrind-dev IRC and it seems that there is still interest in including this feature in valgrind) One refinement that would be useful (if possible) would be the ability to specify a "dummy" source file to each JITted location so that we can filter by only those using the "source file" grouping feature in kcachegrind. If you use this at the moment, JITted code will be mixed in with all of the other "unknown" code in the profile. By allowing the user to specify their own "source file" (rather than, e.g. hard-coding the source file to "JIT"), it would be possible to give different "source files" to different tiers of a multi-tier JIT, which I think would be useful. -- You are receiving this mail because: You are watching all bug changes.
