out-of-bound write

[Niels Möller]

Torbjorn Granlund <tg at gmplib.org> writes:

> I don't think trimming the requirements to a or even b will be doable
> without either:
>
> 1. slowing down the function (by e.g., split up the culprit mpn_mul call
>    into one mpn_mul and one mpn_addmul_1, or
> 2. making a large local allocation for the mpn_mul product.

Would my pet api change help here? I.e., let mpn_mul return, but not
store, the high limb?

> To me, documenting a+1 as required allocation seem like the best
> solution.

Agree (any mpn_mul API change won't happen anytime soon, if ever).

Regards,
/Niels

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