I've now added a configure test for valgrind/memcheck.h, and I've added
code to testsuite/memxor-test.c to use valgrind client requests to tell
it the start and end of the src and dst areas.

I've also added the flag --partial-loads-ok=yes to the VALGRIND variable
in testsuite/Makefile.in. I usually run valgrind with the invocation

  make check EMULATOR='$(VALGRIND)'

Without that flag, I get tons of warnings for both x86_64/memxor.asm and
memxor.c.

It would make sense to add similar client requests to more testcases.

Regards,
/Niels

-- 
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.

_______________________________________________
nettle-bugs mailing list
[email protected]
http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs

Reply via email to