On Wed, 2008-02-20 at 08:15 +0100, Bart Van Assche wrote: > On Feb 19, 2008 10:09 PM, Nicholas Nethercote <[EMAIL PROTECTED]> wrote: > > But programmers should know in advance which bits of memory should be > > shared. Perhaps some client requests could be used which say "this section > > of memory will be shared" or "this section of memory won't be shared" could > > be useful. In the "won't be shared" sections the checking might be a lot > > simpler? > > Hello Nick, > > Sounds nice, but a very important task for data race detection tools > is to detect which data is shared between threads unintentionally.
That's one class of bug but there is another class where data is known to be shared but the locking is insufficient. Checking for the latter but not the former doesn't sound useful but if it gives a significant performance improvement it would be useful to have as an addition. I think the problem with it is you would need to annotate *all* library's linked with the program for it to work and that isn't going to happen easily and would be extensive and hence error prone if it did. Ashley, ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
