Trevor Spiteri <tspit...@ieee.org> writes: Valgrind is reporting the use of uninitialised value(s) in __gmpz_powm_sec for i686 host, though I found no similar issue for x86_64 host. This issue started in 6.3.0, and was not there for 6.2.1.
I tried this, and it looks like a valgrind bug rather than a GMP bug. I inserted a print of the single-limb result in mpz/powm_sec.c, just after the call to mpn_powm_sec. The result is 9 as expected, but valgrind claims that 9 is not initialised. Quite extraordinary that the result can be correct while valgrind says nobody generated any result. I also wrote well-defined garbage to that same location before the mpn_sec_powm call. That proves that the 9 just didn't happen to be there, but that mpn_sec_powm wrote it there. Still valgrind thinks the location is not well-defined. Possibly, valgrind tracks something which it thinks is not well-defined, but that the error becomes delayed? (I cannot reproduce this for a 64-bit build.) -- Torbjörn Please encrypt, key id 0xC8601622 _______________________________________________ gmp-bugs mailing list gmp-bugs@gmplib.org https://gmplib.org/mailman/listinfo/gmp-bugs
