Document flakiness of NON_SIMD_CALL* in comments and the manual.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7279
This commit is contained in:
Nicholas Nethercote
2007-12-05 21:51:50 +00:00
parent 5e06b17d65
commit d17c45b9d1
2 changed files with 17 additions and 1 deletions

View File

@@ -200,7 +200,14 @@ tool-specific macros).</para>
client programs.</para>
<para><command>Warning:</command> Only use these if you
<emphasis>really</emphasis> know what you are doing.</para>
<emphasis>really</emphasis> know what you are doing. They aren't
entirely reliable, and can cause Valgrind to crash.
Generally, your prospects of these working are made higher if the called
function does not refer to any global variables, and does not refer to any
libc or other functions (printf et al). Any kind of entanglement with libc
or dynamic linking is likely to have a bad outcome, for tricky reasons
which we've grappled with a lot in the past.
</para>
</listitem>
</varlistentry>