Sorry, this phrase came from my confusion. Please ignore this phrase. NIIBE Yutaka <gni...@fsij.org> wrote: > The current use of _gcry_mpih_cmp_ui is only at one place. That is, > catching a wrong use case (where no inverse exists) in the function > mpih_invm_odd (libgcrypt/mpi/mpi-inv.c). So, one of these changes would > be possible (in future, if needed). But in such a case, I'd prefer > change of the function name (not cmp_ui, which suggests -1, 0, 1) so > that keeping least surprise.
The topic in this thread is for _gcry_mpih_cmp_lli. -- _______________________________________________ Gcrypt-devel mailing list Gcrypt-devel@gnupg.org https://lists.gnupg.org/mailman/listinfo/gcrypt-devel