Hi all, I tried the new ELPA easyblock on our two computers, and I thought that I did not have to say 'usempi': True in toolchainopts but then it used icc and ifort for linking even of the MPI version and the build broke with lots of unresolved references to mpi_init and all the other mpi calls. After adding 'usempi': True the installation on JURECA, a Haswell cluster worked as expected. On the Skylage cluster however I got --disable-avx512 and I believe that the reason for that is the following: In the log I found == 2019-04-03 09:29:37,471 elpa.py:93 INFO CPU features considered for auto-detection: ['avx', 'avx2', 'avx512', 'vsx', 'sse4_2'] == 2019-04-03 09:29:37,477 elpa.py:102 INFO List of available CPU features: ['3dnowprefetch', 'abm', 'acpi', 'adx', 'aes', 'aperfmperf', 'apic', 'arat', 'arch_perfmon', 'art', 'avx', 'avx2', 'avx512bw', 'avx512cd', 'avx512dq', 'avx512f', 'avx512vl', 'bmi1', 'bmi2', 'bts', 'cat_l3', 'cdp_l3', 'clflush', 'clflushopt', 'clwb', 'cmov', 'constant_tsc', 'cqm', 'cqm_llc', 'cqm_mbm_local', 'cqm_mbm_total', 'cqm_occup_llc', 'cx16', 'cx8', 'dca', 'de', 'ds_cpl', 'dtes64', 'dtherm', 'dts', 'eagerfpu', 'epb', 'ept', 'erms', 'est', 'f16c', 'flexpriority', 'fma', 'fpu', 'fsgsbase', 'fxsr', 'hle', 'ht', 'ibpb', 'ibrs', 'ida', 'intel_ppin', 'intel_pt', 'intel_stibp', 'invpcid', 'lahf_lm', 'lm', 'mba', 'mca', 'mce', 'mmx', 'monitor', 'movbe', 'mpx', 'msr', 'mtrr', 'nonstop_tsc', 'nopl', 'nx', 'ospke', 'pae', 'pat', 'pbe', 'pcid', 'pclmulqdq', 'pdcm', 'pdpe1gb', 'pebs', 'pge', 'pku', 'pln', 'pni', 'popcnt', 'pse', 'pse36', 'pts', 'rdrand', 'rdseed', 'rdt_a', 'rdtscp', 'rep_good', 'rtm', 'sdbg', 'sep', 'smap', 'smep', 'smx', 'spec_ctrl', 'ss', 'sse', 'sse2', 'sse4_1', 'sse4_2', 'ssse3', 'stibp', 'syscall', 'tm', 'tm2', 'tpr_shadow', 'tsc', 'tsc_adjust', 'tsc_deadline_timer', 'vme', 'vmx', 'vnmi', 'vpid', 'x2apic', 'xgetbv1', 'xsave', 'xsavec', 'xsaveopt', 'xtopology', 'xtpr'] which means that avx, avx2, and sse4_2 are found but not avx512, because there are only 'avx512bw', 'avx512cd', 'avx512dq', 'avx512f', 'avx512vl'
Maybe in elpa.py something like
# on macOS, AVX is indicated with 'avx1.0' rather than 'avx'
if 'avx1.0' in avail_cpu_features:
avail_cpu_features.append('avx')
would help, so I added
# on Skylake, AVX512 is indicated with 'avx512bw' rather
than 'avx512'
if 'avx512bw' in avail_cpu_features:
avail_cpu_features.append('avx512')
to elpa.py which indeed results in --enable-avx512 in the configure part
of ELPA. But I don't know which one of the avx512* is the best to use.
Can someone help me?
Regards
Inge Gutheil
--
Inge Gutheil
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany
Phone: +49-2461-61-3135
Fax: +49-2461-61-6656
E-mail:[email protected]
ELPA.
signature.asc
Description: OpenPGP digital signature
