From b30612fef7e6e93431878e475362e3269b44400b Mon Sep 17 00:00:00 2001 From: Philippe Waroquiers Date: Wed, 25 Jul 2012 21:58:40 +0000 Subject: [PATCH] re-re-clarify the doc about registers and flags gdbsrv up-to-date-ness Following discussions on valdev and re-measurement, clarify the clarification. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12784 --- docs/xml/manual-core-adv.xml | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/docs/xml/manual-core-adv.xml b/docs/xml/manual-core-adv.xml index 73179b568c..b7e83b370e 100644 --- a/docs/xml/manual-core-adv.xml +++ b/docs/xml/manual-core-adv.xml @@ -776,9 +776,9 @@ are however some limitations and peculiarities: "stop-at" commands will be obeyed precisely. The downside is that this requires each instruction to be instrumented with an additional call to a gdbserver helper - function, which gives considerable overhead compared to - . Option - has neglectible overhead compared + function, which gives considerable overhead (+500% for memcheck) + compared to . + Option has neglectible overhead compared to . @@ -789,19 +789,20 @@ are however some limitations and peculiarities: or when single stepping, registers and flags values might not be always up to date due to the optimisations done by the Valgrind core. Disabling some optimisations using the following options will increase - the precision of registers and flags values. - An idea of the performance impact for memcheck is given for each option. + the precision of registers and flags values (a typical performance + impact for memcheck is given for each option). - (10% performance impact). + (+5%) ensures + that all integer registers are up to date at each memory access. - (200% performance impact). - - - (250% performance impact). + (+100%) ensures that + all registers and flags values are up to date at each instruction. + Note that the above options can be combined with + (+500%, see above Precision of "stop-at" commands). -- 2.47.2