Using plain malloc will incur a performance penalty on many versions of gcc, which wouldn't be acceptable for MPIR, but we could look into using __builtin_malloc only after testing its availability.
__builtin_malloc should only be used with GCC, though I am surprised to learn that clang is not 100% compatible on that point. Anyway, we've started building flint with clang, so MPIR will also be tested against it in future. Bill. On 3 June 2013 12:33, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 06/03/2013 01:09 PM, Bill Hart wrote: > >> Thanks. I'll take a look and merge it with the next release. >> > > I recommend a different solution, namely using plain malloc() instead of > __builtin_malloc(), or only using __builtin_malloc after testing that it > exists (like you do for __builtin_alloca). That solution is not specific to > any compiler. > > > -- > 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+unsubscribe@**googlegroups.com<mpir-devel%2bunsubscr...@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?hl=en<http://groups.google.com/group/mpir-devel?hl=en> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
