{2023.06}[foss/2023b] LLVM-20.1.5

[Crivella]

Add LLVM-20.1.5 to estack for 5.1.1-2023b

[ocaisa]

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/intel/skylake_avx512

[eessi-bot-aws]

New job on instance eessi-bot-mc-aws for CPU micro-architecture x86_64-intel-skylake_avx512 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2025.07/pr_1143/78477

date	job status	comment
Jul 25 13:53:54 UTC 2025	submitted	job id 78477 awaits release by job manager
Jul 25 13:54:00 UTC 2025	released	job awaits launch by Slurm scheduler
Jul 25 13:59:43 UTC 2025	running	job 78477 is running
Jul 25 14:14:15 UTC 2025	finished	😢 FAILURE (click triangle for details) Details ✅ job output file slurm-78477.out ✅ no message matching FATAL: ❌ found message matching ERROR: ✅ no message matching FAILED: ❌ found message matching required modules missing: ❌ no message matching No missing installations ✅ found message matching .tar.gz created! Artefacts eessi-2023.06-software-linux-x86_64-intel-skylake_avx512-17534524900.tar.gz size: 28 MiB (30188903 bytes) entries: 179 modules under 2023.06/software/linux/x86_64/intel/skylake_avx512/modules/all psutil/6.1.0-GCCcore-13.2.0.lua Z3/4.13.0-GCCcore-13.2.0.lua software under 2023.06/software/linux/x86_64/intel/skylake_avx512/software psutil/6.1.0-GCCcore-13.2.0 Z3/4.13.0-GCCcore-13.2.0 reprod directories under 2023.06/software/linux/x86_64/intel/skylake_avx512/reprod no reprod directories in tarball other under 2023.06/software/linux/x86_64/intel/skylake_avx512 no other files in tarball
Jul 25 14:14:15 UTC 2025	test result	😁 SUCCESS (click triangle for details) ReFrame Summary [ OK ] ( 1/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:x86_64_intel_skylake_avx512+default P: perf: 417.873 timesteps/s (r:0, l:None, u:None) [ OK ] ( 2/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:x86_64_intel_skylake_avx512+default P: perf: 439.073 timesteps/s (r:0, l:None, u:None) [ OK ] ( 3/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /775175bf @BotBuildTests:x86_64_intel_skylake_avx512+default P: latency: 1.79 us (r:0, l:None, u:None) [ OK ] ( 4/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /52707c40 @BotBuildTests:x86_64_intel_skylake_avx512+default P: latency: 1.77 us (r:0, l:None, u:None) [ OK ] ( 5/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /b1aacda9 @BotBuildTests:x86_64_intel_skylake_avx512+default P: latency: 3.43 us (r:0, l:None, u:None) [ OK ] ( 6/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /c6bad193 @BotBuildTests:x86_64_intel_skylake_avx512+default P: latency: 3.73 us (r:0, l:None, u:None) [ OK ] ( 7/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /15cad6c4 @BotBuildTests:x86_64_intel_skylake_avx512+default P: latency: 0.5 us (r:0, l:None, u:None) [ OK ] ( 8/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /6672deda @BotBuildTests:x86_64_intel_skylake_avx512+default P: latency: 0.45 us (r:0, l:None, u:None) [ OK ] ( 9/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /2a9a47b1 @BotBuildTests:x86_64_intel_skylake_avx512+default P: bandwidth: 10744.65 MB/s (r:0, l:None, u:None) [ OK ] (10/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /1b24ab8e @BotBuildTests:x86_64_intel_skylake_avx512+default P: bandwidth: 10645.6 MB/s (r:0, l:None, u:None) [ PASSED ] Ran 10/10 test case(s) from 10 check(s) (0 failure(s), 0 skipped, 0 aborted) Details ✅ job output file slurm-78477.out ❌ found message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case

[ocaisa]

Unfortunately, this is premature as the easyblock is relying on features that are not in 5.1.1:

  File "/tmp/eb-ugedxuw_/eb-y9ntenzf/included-easyblocks-bmcpextt/easybuild/easyblocks/llvm.py", line 425, in _configure_build_targets
    amd_gfx_list = self.cfg.get_amdgcn_cc_template_value("amdgcn_cc_space_sep", required=False).split()
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'EasyConfig' object has no attribute 'get_amdgcn_cc_template_value'. Did you mean: 'get_cuda_cc_template_value'?

[Crivella]

As pointed out this will have to wait until the next version for

• Add support for amdgcn-capabilities configuration option and amdgcn_capabilities easyconfig parameter + related templates, similar to cuda-compute-capabilities easybuilders/easybuild-framework#4860

At that point we should also be able to remove the specific commits as the EC/EB changes will also be in easybuild