Hello > > http://www.csl.cornell.edu/~vince/projects/valsim/ > > > We don't really have official guidelines for adding experimental tools, > other than someone must be willing to maintain it. I think it could be > useful to multiple people using Simpoints, so I think it could be a suitable > addition. I see it's a fairly simple tool (bbv_main.c isn't very long), so > that's a plus.
Yes, it's a relatively straightforward tool. It would be nice to have a completely open-source bbv generating tool available to the general public. I must admit some of my reasons for wanting it merged are a bit selfish; I mainly hate messting around with automake and configure files whenever I want to build the tool on a new machine. I really need to get some test cases too. Trying to get things in shape for merging with a public tree is a good incentive for getting around to lots of testing and code cleanup. > If you're looking up the OSet for every instruction then I can believe that > would cause a big slow-down. I think you can instead do the look-up at > instrumentation-time rather than run-time. You're right, I hadn't thought about that! I've made this change, and now my tool runs at least twice as fast as it used to. Thanks Vince ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
