On 06/03/2013 01:59 PM, leif wrote:
Not performance, but the brokenness to test might actually be related to the use of GCC's *built-in* malloc().
Perhaps, I don't know which GCC-4.3.2 bug this refers to.
If this is the case, it obviously should not be changed to malloc() and the right thing to do is checking for the existence of __builtin_malloc().
-- 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.
