It looks like you configured your broadwell as a generic x86_64 instead of as a haswell (as per your patch). This means that it wasn't using anything other than generic assembly for the build, and hence the tuning values will be way off.
Perhaps you can force it to build as a haswell and then run tune again. On 14 February 2017 at 10:24, Isuru Fernando <isu...@gmail.com> wrote: > Attached are tuning values for nehalem, ivybridge, broadwell and skylake. > (Also cpuinfo for the broadwell one) > > Isuru Fernado > > On Tue, Feb 14, 2017 at 1:29 PM, 'Bill Hart' via mpir-devel < > mpir-devel@googlegroups.com> wrote: > >> Apparently if you have a very recent machine, yasm may fail to build the >> assembly files for your architecture. To get around this, install the >> latest yasm [1] and use MPIR's --with-system-yasm option. >> >> If your system is recent and detects as core2 or k8 or simply x86_64 or >> something else obviously out-of-date, when tuning, please also send us a >> copy of cat /proc/cpuinfo so we can add support for your processor to MPIR. >> >> Bill. >> >> [1] http://yasm.tortall.net/ >> >> On 13 February 2017 at 18:41, Bill Hart <goodwillh...@googlemail.com> >> wrote: >> >>> Hi all, >>> >>> MPIR has been modified recently, and new tuning crossovers have been >>> added. >>> >>> If you have a machine that you want MPIR to run fast on, we would really >>> appreciate help getting tuning values for your machine. Here is how. >>> >>> git clone https://github.com/wbhart/mpir >>> cd mpir >>> ./configure --enable-gmpcompat >>> make -j4 >>> make check >>> cd tune >>> make tune >>> >>> Please attach the tuning values that are printed to this post. Please >>> ensure that the first line is not missing, e.g. >>> >>> Parameters for ./mpn/x86_64/k8/k10/k102/gmp-mparam.h >>> >>> as this tells us what machine the values are for. >>> >>> If the tuning program crashes, or starts to take too long, just send us >>> the values you have. >>> >>> Any help that people can provide is really appreciated. >>> >>> Note that we DON'T require tuning values for the following arches: >>> >>> mpn/x86_64/k8/k10/k102 >>> mpn/x86_64/haswell >>> >>> If someone already attached values for your arch, no need to supply them >>> again. >>> >>> Bill. >>> >>> >> -- >> 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 https://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 https://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 https://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
