Ah, no sorry, ignore that. It doesn't. Same problem.
On 2 April 2014 00:25, Bill Hart <goodwillh...@googlemail.com> wrote: > It compiles correctly if it is declared with __GMP_PROTO instead of _PROTO. > > No idea why!! > > Bill. > > > On 2 April 2014 00:21, Bill Hart <goodwillh...@googlemail.com> wrote: > >> I think it is the compiler, not the linker. For a call to mpn_add_n (also >> assembly) it emits: >> >> call *__imp___gmpn_add_n(%rip) >> >> For a call to mpn_store, it emits: >> >> call __gmpn_store >> >> The question is, why? >> >> Bill. >> >> >> On 2 April 2014 00:10, Bill Hart <goodwillh...@googlemail.com> wrote: >> >>> It's nothing to do with the MPN_ZERO macro. A straight call to mpn_store >>> segfaults. >>> >>> Bill. >>> >>> >>> On 1 April 2014 23:59, Bill Hart <goodwillh...@googlemail.com> wrote: >>> >>>> Yeah that seems more likely, doesn't it. >>>> >>>> Why on earth for just that one function though. It's totally bizarre. >>>> >>>> >>>> On 1 April 2014 23:57, Jean-Pierre Flori <jpfl...@gmail.com> wrote: >>>> >>>>> Or maybe that's an binutils/ld bug as I guess ld is in charge of >>>>> putting the right address in the call[q] arg. >>>>> >>>> >>>> >>> >> > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
