Broad valgrind run

Torbjörn Granlund tg at
Sun Jun 7 12:13:45 UTC 2015

Perhaps our private red-zones are obsolete now that we have valgrind and
also vaeious memcheck compiler features?

I am not familiar with the valgrind annotations you're using and what
benefits they might bring.  It would be nice to not require code
annotations, as these take time to write, debug and maintain.

An alternative to valgrind is gcc's -fsanitize=address and similar
options to clang (assuming we can find a clang usable for GMP
compilation).  Here too, we shoiuld probably remove our private

Please encrypt, key id 0xC8601622

More information about the gmp-devel mailing list