From 3801eaa1aad1a55f78cf60fc3e1af0020174ed19 Mon Sep 17 00:00:00 2001 From: Bart Van Assche Date: Wed, 2 Jul 2008 11:50:37 +0000 Subject: [PATCH] Added a few extra notes. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8335 --- exp-drd/docs/drd-manual.xml | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/exp-drd/docs/drd-manual.xml b/exp-drd/docs/drd-manual.xml index 5a098b7506..d4e1d4cf33 100644 --- a/exp-drd/docs/drd-manual.xml +++ b/exp-drd/docs/drd-manual.xml @@ -1073,6 +1073,12 @@ source file name and the line number where the data race has been detected (omp_matinv.c:203). + +Note: DRD reports errors on the libgomp library +included with gcc 4.2.0 up to and including 4.3.1. This might indicate +a race condition in the POSIX version of libgomp. + + For more information about OpenMP, see also openmp.org. @@ -1097,6 +1103,15 @@ For more information about OpenMP, see also Valgrind. + + + Most applications will run between 20 and 100 times slower under + DRD than natively. Applications which perform very much mutex + lock / unlock operations however will run too slow to be usable + under DRD. Examples are Firefox and Nautilus. This will be + addressed in a future DRD version. + + Of the two POSIX threads implementations for Linux, only the @@ -1126,13 +1141,20 @@ For more information about OpenMP, see also behavior is caused by Valgrind or by gcc. + + + When address tracing is enabled, no information on atomic stores + will be displayed. This functionality is easy to add + however. Please contact the Valgrind authors if you would like + to see this functionality enabled. + + If you compile the DRD source code yourself, you need gcc 3.0 or later. gcc 2.95 is not supported. - -- 2.47.2