blob: bbfdc108c0db8d3787cc9e30a3783e59f7c33450 [file] [log] [blame]
bart14af5962008-07-01 13:46:33 +00001Last updated July 1, 2008.
bart055c56b2008-02-17 18:13:00 +00002~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sewardjaf44c822007-11-25 14:01:38 +00003
4
5Data-race detection algorithm
6~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bart99554152008-04-14 16:11:50 +00007- Memory pool support.
bart0e3a0be2008-07-03 16:23:17 +00008- Find out why DRD reports an error on the POSIX implementation of libgomp.so.
bartaae367c2008-04-19 15:17:08 +00009- Add locking order checking. Start from the following information:
10 * http://sourceforge.net/mailarchive/message.php?msg_id=alpine.LNX.1.10.0803270822080.17890%40mudge.stoecker.eu
11 * http://lwn.net/Articles/185605/
12 * http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/lockdep-design.txt;h=488773018152056ea159685e732e42452a7ae142;hb=HEAD
bart906ef122008-05-25 18:11:32 +000013- Make sure tc14_laog_dinphils is run during exp-drd regression tests
14 (only possible after locking order checking is implemented).
bart0e3a0be2008-07-03 16:23:17 +000015- Find out why no variable name information is printed for races
16 detected in parallel sections of OpenMP programs. An example:
bart7b8e43b2008-03-16 10:57:02 +000017 ./vg-in-place --tool=exp-drd exp-drd/tests/omp_prime 4 -t 2
bart7f912c02008-07-07 08:45:55 +000018- Report races in glibc on stdout / stderr back to glibc maintainers.
bart3bdf1252008-03-23 14:32:21 +000019
sewardjaf44c822007-11-25 14:01:38 +000020
21Testing
22~~~~~~~
barte4da24f2008-06-17 14:19:04 +000023- Measure the performance and the memory overhead of exp-drd on the PARSEC
24 benchmark (http://parsec.cs.princeton.edu/license.htm).
25- Test with Synfig Studio (see also http://bugs.kde.org/show_bug.cgi?id=158555)
26- Test with a multithreaded Python application.
sewardjaf44c822007-11-25 14:01:38 +000027
28
29Documentation
30~~~~~~~~~~~~~
bart7f912c02008-07-07 08:45:55 +000031- Add comment on double checked locking.
32- Add comment on circular buffers.
bartfbccd7f2008-05-10 13:00:27 +000033- Explain how to handle transactions (with regard to locking order).
bart59bdc762008-05-15 11:45:08 +000034- Continue the discussion on the Valgrind mailing list about docbook and
35 'make dist'. See also http://bugs.kde.org/show_bug.cgi?id=162121.