David Miller <da...@davemloft.net> writes: And I want to take this opportunity to mention that 'try' is very non-useful at times for testing newly coded routines. I don't use it for that.
It seems to perform several unrelated mpn calculations during initialization before it does the primary test of the routine in question. It indeed does. If those initialization mpn calculations use the routine being tested, we can never end up getting to the test itself if there's a bug in the new code, resulting in either erratica behavion or a crash. This is very hard to diagnose compared to if the actual test itself failed and 'try' gave a useful diagnostic with the mpn "expected vs. obtained" dump. The other files in tests/devel are better suited for development. They are old and ugly, but you cannot have everything. Now I used shift.c -DOPERATION_rshift -DCLOCK=1593000000 -DPLAIN_RANDOM -DSIZE=40 \ -DRANDOM -DTIMES=1 The CLOCK argument is stupidly reqired. -DPLAIN_RANDOM disables the special random numbers with long strides of ones and zeros. -DRANDOM uses a random size limited by the SIZE argument. The TIMES argument disables timing tests. I have cleaned-up tests which I might check in one of these days. -- Torbjörn _______________________________________________ gmp-devel mailing list gmp-devel@gmplib.org http://gmplib.org/mailman/listinfo/gmp-devel
