Ciao, Il Dom, 20 Novembre 2016 10:22 pm, Niels Möller ha scritto: > I've checked in a fix for this. > https://gmplib.org/repo/gmp/rev/6a2a9d2f639c > > Marco, would mind having a look at the reorganized test? I deleted
Agreed, much cleaner than mine. > It would be cool if -fsanitizer=undefined could cooperate with valgrind, > and not complain immediately when there's an undefined value, but > instead taint that value, and complain if it or anything which depends > in it is ever used for a branch condition, memory access or system call. > (And strictly speaking, that would make sense only for implementation > defined behaviour, not undefied behaviour, I guess). Strictly speaking that would make sense for "undefined value", but "undefined behaviour" may mean "illegal instruction" or whatever... The version I wrote for this test did not fully respect C standard, now it's better :-) Best regards, mb -- http://bodrato.it/ _______________________________________________ gmp-devel mailing list gmp-devel@gmplib.org https://gmplib.org/mailman/listinfo/gmp-devel
