> I am writing a byte code profiler for gst and had preliminary success. > Right now it can record detail call graph and number of byte code > executed in each method and export a report that is compatible with > callgrind (valgrind) thus viewable with kcachegrind.
Cool. I had a minimal profiler based on Bags, but it didn't record callgraphs. > It will be small (~100 lines of c code and ~200 lines of smalltalk) and > intimate to the virtual machine so I think the best place for it to be > is in the gst distribution itself. Is something like this desired? If > so, I can polish it up, refresh it with the latest git head and post it > as a couple of patches. Of course. Anything contributed is acceptable. However, you'll need to sign copyright papers. I'll follow up privately. Paolo _______________________________________________ help-smalltalk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-smalltalk
