Dear Jure,
We recompiled the last 2 toolchains for skylake (2017{a,b}), and we made
for the older stuff symlinks pointing to broadwells. If you recompile,
you will experience some compiler errors using AVX512 (infinite loops)
(glog-0.3.5-intel-2017b, GStreamer 0.10.36 intel-2017b,
util-linux-2.29.2-intel-2017a) and maybe others as well. I am not 100%
sure that recompilation is necessary, maybe in the case of most used
software.
Concerning the compilers, Skylake is supported from GCC 5.3.0 and intel
15.0.1, so foss-2016b or later or intel-2015a or later. (as a matter of
fact GCC 4.9 already knows AVX-512, but that was made for Xeon Phi x200)
Sincerely,
Balazs
On 26/03/2018 10:01, Jure Pečar wrote:
Hi all,
We initially deployed easybuild with three repositories for nehalem,
sandybridge and haswell. Now with availability of skylake and znver1 the
question arises what is the best way to introduce new arch.
Does it make sense to rebuild everything from foss-2015 and -2016 on new
machines? If I understand things correctly, only foss-2017b can start taking
advantage of avx512.
I assume you want to provide all the existing modules under all architectures,
to provide uniform view to the users. Can the modules subdir from eg haswell
can just be copied over under skylake? Modulefiles have full paths so I assume
this should work?
Currently I just symlink znver1 to haswell and it seems to work fine, no
illegal instructions or unexplained crashes. How do other sites deal with this?
Do we have some notes online somewhere on this?
Also, looking forward to 3.6 with "vectorize by default" for gcc.
--
HPC consultant
HPC/VSC Support and System Administration
Computing Center
ULB/VUB
Avenue Adolphe Buyllaan 91 - CP 197
1050 Brussels
Belgium
