mpz reuse test takes too much time

[Niels Möller]

nisse at lysator.liu.se (Niels Möller) writes:

> and for a five-operand
> function like gcdext, I can't easily get the correct count

Actually, in the case of gcdext, there are three result arguments, which
mustn't overlap with each other.

So there are only 16 cases of valid overlap when all operands are
provided, and 9 cases of valid overlap when the t argument is NULL.

> Then we shouldn't need more than a few 100000 calls cover all cases, and
> we shouldn't need very large operands.

Hmm, that's perhaps too pessimistic. Since many of the 160 mpz functions
have only one or two mpz arguments, average number of cases per function
is likely < 10. And then we should need < 10000 calls total, which I
think is on the same order as several other tests.

Am I missing something?

Regards,
/Niels

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