The only thing we need is the output of cat /proc/cpuinfo under Linux. Broadwell is supported in this release, we just haven't optimised for it. That would be 3-6 months of full time work, so there's no chance of it happening in this release.
Bill. On 18 February 2017 at 20:24, <wrai...@morpheus.net> wrote: > Hello Bill, > > I have two identical Broadwell computers, except that one runs Windows 7 > Pro x64 and the other runs Linux x64 (based on CentOS 6.7). The processor > in both is an Intel Xeon E5-2687W v4. I did 3 different configures/tunes > on each system, in 3 different directories so there would be no cross > contamination. Configure originally chose k8 for both systems. The > commands I ran were: > =================== > On Windows: > ./configure --enable-gmpcompat --disable-shared > ./configure --enable-gmpcompat --disable-shared --build=haswell-w64-mingw32 > ./configure --enable-gmpcompat --disable-shared > --build=broadwell-w64-mingw32 > make -j4 > make check > cd tune > make tune > > Both make and make check completed successfully for all 3 builds. > However, all 3 tune programs ended up crashing. I'm not sure why, but I'm > including the screen output in case you can see what the problem was. > > =================== > On Linux: > ./configure --enable-gmpcompat --disable-shared > ./configure --enable-gmpcompat --disable-shared > --build=haswell-unknown-linux-gnu > ./configure --enable-gmpcompat --disable-shared > --build=broadwell-unknown-linux-gnu > make -j4 > make check > cd tune > make tune > > Both make and make check completed successfully for all 3 builds. On > Linux all 3 tune programs completed successfully. > =================== > > All together I'm including 13 text files, the 6 config.log files, the 6 > tune screen outputs, and the "cat /proc/cpuinfo" from my Linux computer. > I'm putting them in a zip file, but if this doesn't make it to the mailing > list, I can resend with all 13 text files directly attached. > > Also, I see that you mentioned you would like some tests run on different > assembly files to see which will run faster on Broadwell. Could you let me > know what tests you would like me to run, and also how to run these tests. > I'd be happy to help if I can. I would personally like to see Broadwell > supported in this release, but I know that will take a lot of work. Let me > know if I can help or if there is any other information I can provide. > > -David C. > > On 2/14/2017 4:16 AM, 'Bill Hart' via mpir-devel wrote: > >> 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 >> <mailto: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 <mailto: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 >> <mailto: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 >> <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 >> <mailto:mpir-devel+unsubscr...@googlegroups.com>. >> To post to this group, send email to mpir-devel@googlegroups.com >> <mailto:mpir-devel@googlegroups.com>. >> Visit this group at https://groups.google.com/group/mpir-devel >> <https://groups.google.com/group/mpir-devel>. >> For more options, visit https://groups.google.com/d/optout >> <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 >> <mailto:mpir-devel+unsubscr...@googlegroups.com>. >> To post to this group, send email to mpir-devel@googlegroups.com >> <mailto:mpir-devel@googlegroups.com>. >> Visit this group at https://groups.google.com/group/mpir-devel >> <https://groups.google.com/group/mpir-devel>. >> For more options, visit https://groups.google.com/d/optout >> <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 >> <mailto:mpir-devel+unsubscr...@googlegroups.com>. >> To post to this group, send email to mpir-devel@googlegroups.com >> <mailto: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.
