History log of /external/valgrind/exp-bbv/tests/amd64-linux/fldcw_check.S
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
b1f90e040439f3eec6ae82d71dc0aabb725c6b30 03-Oct-2013 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Change some inline assembler so it is no longer rejected by clang
as suggested by John Reiser and Greg Parker.
It seems that GCC has a more relaxed attitude about what it accepts
as valid input.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13610 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/exp-bbv/tests/amd64-linux/fldcw_check.S
c98d2af90d010d78afc547141a61ca6029240cc6 18-Aug-2009 vince <vince@a5019735-40e9-0310-863c-91ae7b9d1cf9> Work around a binutils limitation on SuSE 9.1
by hand-coding the 32-bit fldcw instructions,
as the assembler gives an error when
trying to assemble them. The generated binary
is identical to one generated on a system
with working binutils.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10838 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/exp-bbv/tests/amd64-linux/fldcw_check.S
dbebecc2bf00530ce09b3658641d1514d807aeee 14-Jul-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add exp-bbv to the tool-suite. I'm seeing a couple of amd64-linux test
failures, but they can be fixed up in-repo. This resolves bug 198395.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10444 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/exp-bbv/tests/amd64-linux/fldcw_check.S