I have dealt with all the nontrivial tickets I believe. Here is the list of remaining tickets for this release:
https://github.com/wbhart/mpir/issues?milestone=1&state=open I think essentially all of those are either invalid, will get moved to the next release or are trivial. Bill. On 25 March 2014 00:45, Bill Hart <goodwillh...@googlemail.com> wrote: > I was amazed MPIR built fine on an AIX IBM Power7 machine. > > Bill. > > > On 25 March 2014 00:42, Bill Hart <goodwillh...@googlemail.com> wrote: > >> I have now tuned o x86/pentium4/sse2, sparc32, sparc64, ppc32, ppc64. >> >> That just leaves bobcat, atom, arm, mips32, mips64. >> >> Bill. >> >> >> On 24 March 2014 17:17, Bill Hart <goodwillh...@googlemail.com> wrote: >> >>> I have now assigned 36 open tickets to the 2.7 release. I'm sure more >>> will be added, but at least we now have some measure of how far we are from >>> a release. >>> >>> Next I will finish off tuning on the few other machines I have available. >>> >>> Bill. >>> >>> >>> On 21 March 2014 21:42, Bill Hart <goodwillh...@googlemail.com> wrote: >>> >>>> >>>> >>>> >>>> On 21 March 2014 21:26, leif <not.rea...@online.de> wrote: >>>> >>>>> Bill Hart wrote: >>>>> >>>>>> I have now tuned on the following architectures: >>>>>> >>>>>> core2, penryn, k102, netburst, k8, k10, bulldozer, westmere, >>>>>> sandybridge, piledriver, nehalem, core2, ia64. >>>>>> >>>>>> I don't have tuning values for: >>>>>> >>>>>> x86 (any kind), bobcat, atom, arm, mips32, mips64, sparc32, sparc64, >>>>>> ppc32, ppc64. >>>>>> >>>>>> If anyone can contribute any of the above, please do. >>>>>> >>>>>> Bill. >>>>>> >>>>> >>>>> Fresh tuning values for Bobcat (AMD E-450) are on the way; I've >>>>> meanwhile run tuneup 20 times while the machine was otherwise idle... (GCC >>>>> 4.8.0 on Ubuntu 10.04.4 x86_64, FWIW). >>>>> >>>>> >>>> Fantastic. However, we need to know one thing before getting bobcat >>>> tuning values: which is faster, mpn/x86_64/bobcat/sqr_basecase.as or >>>> mpn/x86_64/sqr_basecase.asm. >>>> >>>> To find out, could you do the following: >>>> >>>> ./configure >>>> make >>>> cd tune >>>> make speed >>>> ./speed -s 1-40 mpn_sqr_basecase >>>> >>>> {delete mpn/x86_64/bobcat/sqr_basecase.as} >>>> ./configure >>>> make clean >>>> make >>>> cd tune >>>> make speed >>>> ./speed -s 1-40 mpn_sqr_basecase >>>> >>>> If the second set of timings looks lower, leave it as it is when doing >>>> make tune, (otherwise -- unlikely -- put mpn/x86_64/bobcat/ >>>> sqr_basecase.as back, ./configure; make clean; make). >>>> >>>> Now it should be fine to do make tune. >>>> >>>> This step only needs to be done for bobcat. >>>> >>>> I'll presumably provide tuning values for Pentium 4 Prescott (x86) >>>>> tomorrow; MPIR's current cpuid.c still ("mis"-)detects that CPU (family 15 >>>>> model 3; same for model 4) as a stock Pentium 4 though. There's currently >>>>> no special assembly code for Prescott (using SSE3/PNI, say), but GCC is >>>>> fed >>>>> with '-march=pentium4 -mtune=pentium4' instead of '-march=prescott >>>>> -mtune=prescott'. >>>>> >>>> >>>> Is it 64 bit? If not, we don't have any SSE3 code in MPIR. We only go >>>> up to SSE2 on the x86 branch. >>>> >>>> If it is 64 bit, you can force it to build as netburst, that's about >>>> it, i.e. --build=netburst-unknown-linux >>>> >>>> >>>>> >>>>> If it's of any use, I could also try to revive a Pentium III >>>>> (Coppermine) and tune on that. >>>>> >>>> >>>> That would be fun. :-) But it's not important if you don't have time. >>>> We assume people are using more recent processors if they want performance. >>>> >>>> Bill. >>>> >>>> >>>>> >>>>> >>>>> -leif >>>>> >>>>> -- >>>>> () The ASCII Ribbon Campaign >>>>> /\ Help Cure HTML E-Mail >>>>> >>>>> -- >>>>> 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. >>>>> >>>> >>>> >>> >> > -- 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.
