Difference between revisions of "Other Dev Tools"
Hackerpilot (talk | contribs) |
(Section about the excellent, interactive D compiler.) |
||
Line 25: | Line 25: | ||
This will create a file called '''callgrind.out.27497.demangled''' that you can then view using KCachegrind. | This will create a file called '''callgrind.out.27497.demangled''' that you can then view using KCachegrind. | ||
+ | |||
+ | |||
+ | == Interactive D Compiler == | ||
+ | |||
+ | If you want to see the assembly your D code compiles to, please use the following [http://d.godbolt.org/ Interactive D compiler]. |
Revision as of 16:15, 26 February 2013
Valgrind helper
The Valgrind plugin Callgrind can be used to profile D code, but it does not know how to handle D's mangled names. This program can be used to clean up the callgrind.out.nnnnn file so that tools like KCachegrind can display them more legibly.
Code
dcallgrind.d
import std.stdio;
import std.demangle;
import std.regex;
import std.conv;
auto re = ctRegex!(`(_D\d[\w_]+)`);
void main(string[] args)
{
auto isStdin = args.length == 1;
auto inFile = isStdin ? stdin : File(args[1]);
auto outFile = isStdin ? stdout : File(args[1] ~ ".demangled", "w");
foreach (l; inFile.byLine(KeepTerminator.yes))
outFile.write(replace!(a => demangle(to!string(a.hit)))(l, re));
}
Usage
./dcallgrind callgrind.out.27497
This will create a file called callgrind.out.27497.demangled that you can then view using KCachegrind.
Interactive D Compiler
If you want to see the assembly your D code compiles to, please use the following Interactive D compiler.