Can we add another column to the wiki page for the build and tune results: Can we show the architecture as printed by config.guess, e.g. k8 or nehalem or core2 or penryn, etc.
Bill. On 12 May 2010 17:38, Bill Hart <[email protected]> wrote: > That shouldn't be necessary in this case. We simply need to remove all the old > > #define GCDEXT_THRESHOLD 0 /* always */ > > from the gmp-mparam.h files. Default tuning parameters are provided if > this is missing. > > Bill. > > On 12 May 2010 17:32, Jason Moxham <[email protected]> wrote: >> After tuning atom passes . >> I've done tuning for K7 and atom . >> >> Perhaps we should put in some "asserts" to check that the params supplied >> satisfy the required conditions ,like >> >> #if ! TUNED_BUILD && TOOM3_THRESHOLD < 3 >> #error bad params >> #endif >> >> >> On Wednesday 12 May 2010 17:20:34 Bill Hart wrote: >>> Oh yeah, that's what's causing the test failures on k8. This hasn't >>> been tuned for yet. We can't do testing until the tuning is done. >>> >>> On 12 May 2010 17:14, Jason Moxham <[email protected]> wrote: >>> > On Wednesday 12 May 2010 17:04:45 Bill Hart wrote: >>> >> The test failure on flavius is my new gcdext test code. I'll look into >>> >> it right now. >>> > >>> > and on atom , although i've not tuned it yet >>> > >>> >> Bill. >>> >> >>> >> On 12 May 2010 16:15, Minh Nguyen <[email protected]> wrote: >>> >> > Hi folks, >>> >> > >>> >> > I'm currently building revision 2923 on machines within the Skynet and >>> >> > Sage clusters. So far, the build, test, and tuning results are posted >>> >> > to the following wiki page: >>> >> > >>> >> > http://wiki.sagemath.org/mpir/BuildFarm/mpir-2.0.1 >>> >> > >>> >> > Most of the tuning are done. I still have some more results to post to >>> >> > that wiki page. In the meantime, people are invited to build, test, >>> >> > tune the current revision of MPIR and report the results. Please test >>> >> > and report your results. >>> >> > >>> >> > -- >>> >> > Regards >>> >> > Minh Van Nguyen >>> >> > >>> >> > -- >>> >> > 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. >>> > >>> > -- >>> > 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. >> >> -- >> 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. >> >> > -- 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.
