Oh, naturally FLINT makes many other calls to GMP for other functions in this computation.
Bill. 2008/11/1 Bill Hart <[EMAIL PROTECTED]>: > By the way, one doesn't necessarily expect much difference between > these graphs as the integer GCD's being computed by FLINT are small. > But at least we will be able to tell if Jason's changes broke anything > performance wise. > > Bill. > > 2008/11/1 Bill Hart <[EMAIL PROTECTED]>: >> Hi all, >> >> I'm running a profile of a FLINT module which relies heavily on mpir, >> and particularly uses a lot of calls of gcd. >> >> The profile is of FLINT against Magma. The first graph compares mpir >> pre Jason's patch with Magma. >> >> http://sage.math.washington.edu/home/wbhart/flint-trunk/graphing/gcd5.png >> >> The second graph compares mpir post Jason's patch, with Magma. >> >> http://sage.math.washington.edu/home/wbhart/flint-trunk/graphing/gcd6.png >> (still generating automatically as I write). >> >> The blue dots are where FLINT wins, the red where Magma wins, the >> black where they are even. >> >> The problem is to compute polys f, g and h with log_2(length) given by >> the bottom axis and log_2(bits) given by vertical axis of the graph, >> where length is the length of the polynomial f, g and h and bits is >> the number of bits per coefficient (which are uniformly randomly >> generated). >> >> Once f, g and h are computed, I compute gcd(f*h, g*h). Note the first >> column of the graph is basically where FLINT is performing GCD of >> length 1 polynomials, i.e. straight integer GCD. It calls directly to >> GMP for this. It is relevant that the brown spots at the top of that >> column disappear post Jason's patch. >> >> Bill. >> >> 2008/11/1 Bill Hart <[EMAIL PROTECTED]>: >>> Jason, first bug report. When I build mpir with your patches (I have >>> got the mpir repo working locally for me only - hopefully Michael will >>> help me with the apache export so everyone else can get access again), >>> I get warning messages in the compile on sage.math. >>> >>> gcd.c: In function 'mpz_rgcd': >>> gcd.c:167: warning: implicit declaration of function 'mpn_rgcd' >>> gcd.c: In function 'mpz_bgcd': >>> gcd.c:171: warning: implicit declaration of function 'mpn_bgcd' >>> gcd.c: In function 'mpz_sgcd': >>> gcd.c:175: warning: implicit declaration of function 'mpn_sgcd' >>> gcd.c: In function 'mpz_ngcd': >>> gcd.c:179: warning: implicit declaration of function 'mpn_ngcd' >>> >>> It seems to build ok otherwise. >>> >>> Bill. >>> >>> 2008/11/1 Jason Martin <[EMAIL PROTECTED]>: >>>> >>>> On Fri, Oct 31, 2008 at 9:11 PM, mabshoff >>>> <[EMAIL PROTECTED]> wrote: >>>>> [snip] >>>>> For me the highest priority item is the Moller's gcd code which has >>>>> already been merged. What is the status of the code, i.e. performance, >>>>> any known bugs, etc? >>>>> >>>>> Cheers, >>>>> >>>>> Michael >>>> >>>> Hi Michael, >>>> >>>> I haven't tested Moller's code beyond the standard make check test >>>> suite (which passes all tests). I also haven't done any speed tests >>>> other than the most rudimentary checks. So if anyone has some >>>> suggestions for test cases, I'd be happy to try them out. Likewise, >>>> if anyone has any bug reports for the gcd code, let me know and I'll >>>> attempt to figure it out. >>>> >>>> >>>> --jason >>>> >>>> >>>> >>>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
