OK, I see. That issue is Windows specific due to the OPERATION_blah things not being defined by configure scripts, etc.
No problem. That looks fine to me. The other way of doing it is to simply define a macro and invoke it numerous times. That could all be done in the logops_n.c file. I recall this is what Neils Moller did for his gcd functions, e.g. he had bgcd, sgcd, ngcd, etc, functions, all defined by macros. See mpz/gcd.c in http://www.lysator.liu.se/~nisse/archive/gmp-gcd-3.tar.gz This won't work on linux though I think, as for some platforms there is assembly code for these logops functions and we actually need to respect the OPERATION_blah things. So probably best to stick with what you did. Bill. On 25 May 2010 17:12, Cactus <rieman...@googlemail.com> wrote: > On May 25, 4:27 pm, Bill Hart <goodwillh...@googlemail.com> wrote: >> Do we really need logops.c and logops_n.c. Should we do some kind of >> rationalisation? > > I am open to suggestions :-) > > I don't know how to get logops_n.c working on its own - I assume that > it needs another file that includes it repeatedly with the various > OPERATION_??? defines set to specialise it. > > I could have written logops.c this way but it was more bother than it > was worth. > > Brian > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to mpir-de...@googlegroups.com. > To unsubscribe from this group, send email to > mpir-devel+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-de...@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
