|
From: <sv...@va...> - 2008-03-23 14:32:24
|
Author: bart Date: 2008-03-23 14:32:21 +0000 (Sun, 23 Mar 2008) New Revision: 7761 Log: Updated documentation. Modified: trunk/exp-drd/TODO.txt trunk/exp-drd/docs/README.txt Modified: trunk/exp-drd/TODO.txt =================================================================== --- trunk/exp-drd/TODO.txt 2008-03-23 13:17:52 UTC (rev 7760) +++ trunk/exp-drd/TODO.txt 2008-03-23 14:32:21 UTC (rev 7761) @@ -4,26 +4,15 @@ Data-race detection algorithm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- Implement segment merging, such that the number of segments per thread - remains limited even when there is no synchronization between threads. -- Add locking order checking. -- Discuss on the Valgrind mailing list how to make it possible to call - POSIX thread synchronization primitives from client code (drd_intercepts.c) - without triggering Valgrind's redirection mechanism. - Make sure -v works again with exp-drd. +- Add locking order checking. - Continue the discussion on the Valgrind mailing list about docbook and 'make dist'. -- Continue the discussion on the Valgrind mailing list about -Wformat. -- Enable format string checking for DRD during compilation. -- Propose to modify tl_assert() / vg_assert() such that it uses - __builtin_expect. - Explain on the Valgrind mailing list the difference between a bus lock and acquire / release labels. - Add configure tests for the name of the 'kind' member in pthread_mutex_t. - Find out why a race is reported on std::string::string(std::string const&) (stc test case 16). -- Find out why no races are reported on matinv_openmp.c when "private(k)" is - removed. - Add support for objects that are shared over threads and that use reference counting, e.g. std::string -- no races should be reported on the reference count. @@ -35,18 +24,14 @@ - Find out why no line number or variable name information is printed for races detected in parallel sections of OpenMP programs. An example: ./vg-in-place --tool=exp-drd exp-drd/tests/omp_prime 4 -t 2 -- Find a way for suppressing races reported on _IO_2_1_stdout. This race is - triggered by calling printf() from more than one thread. Examples (AMD64): - ./vg-in-place --tool=exp-drd exp-drd/tests/tc21_pthonce - Find out why 'matinv 400' runs faster in 32-bit mode than in 64-bit mode on the same CPU. - testing on PPC and AIX (current implementation is only tested on X86 and AMD64). - Convert the array in drd_thread.c with thread information into an OSet. -- Performance testing and tuning. -- Optimize run time of the following test case: - ./vg-in-place --tool=exp-drd exp-drd/tests/matinv 100 +- Performance testing and tuning, a.o. for kate / knode / open office / matinv. + Testing ~~~~~~~ - testing with more complex multithreaded test programs. @@ -68,13 +53,3 @@ ~~~~~~~~~~~ - Does not work with a glibc library compiled with linuxthreads -- NPTL is required for proper operation. - - -Known bugs -~~~~~~~~~~ -- Gets killed by the OOM handler for realistically sized applications, - e.g. knode and OpenOffice. -- [x86_64] Reports "Allocation context: unknown" for BSS symbols on AMD64 - (works fine on i386). This is a bug in Valgrind's debug info reader - -- VG_(find_seginfo)() returns NULL for BSS symbols on x86_64. Not yet in - the KDE bug tracking system. Modified: trunk/exp-drd/docs/README.txt =================================================================== --- trunk/exp-drd/docs/README.txt 2008-03-23 13:17:52 UTC (rev 7760) +++ trunk/exp-drd/docs/README.txt 2008-03-23 14:32:21 UTC (rev 7761) @@ -301,10 +301,7 @@ Future DRD Versions ------------------- The following may be expected in future versions of DRD: -* Drastically reduced memory consumption, such that realistic applications can - be analyzed with DRD. * A lock dependency analyzer, as a help in deadlock prevention. -* Faster operation. * More extensive documentation. * Support for PowerPC CPU's. |