|
| 1 | +--- |
| 2 | +authors: [julianmorillo] |
| 3 | +date: 2026-05-12 |
| 4 | +slug: lfoss-riscv |
| 5 | +--- |
| 6 | + |
| 7 | +# `lfoss/2025b` now available in the EESSI RISC-V stack |
| 8 | + |
| 9 | +The EESSI RISC-V software stack available through the `dev.eessi.io/riscv` repository |
| 10 | +now includes the `lfoss/2025b` toolchain. |
| 11 | + |
| 12 | +This is an important milestone for the RISC-V enablement work in EESSI, since it brings a |
| 13 | +modern LLVM-based software toolchain to the growing collection of software available for |
| 14 | +RISC-V systems through EESSI. |
| 15 | + |
| 16 | +<!-- more --> |
| 17 | + |
| 18 | +The RISC-V software stack is distributed through the EESSI development repository |
| 19 | +infrastructure and is intended for experimentation, testing, and early adoption of RISC-V |
| 20 | +support in EESSI. |
| 21 | + |
| 22 | +## What is `lfoss` |
| 23 | + |
| 24 | +`lfoss` is the LLVM-based counterpart to the widely used `foss` toolchain in EESSI and |
| 25 | +EasyBuild ecosystems. |
| 26 | + |
| 27 | +Where `foss` is centered around GCC, the `lfoss` family uses LLVM/Clang while still |
| 28 | +providing the familiar scientific software stack components such as MPI, BLAS/LAPACK, FFT |
| 29 | +libraries, and related HPC tooling. |
| 30 | + |
| 31 | +The availability of `lfoss/2025b` on RISC-V is particularly relevant because LLVM's RISC-V |
| 32 | +backend has matured significantly in recent years, making it increasingly viable for HPC |
| 33 | +and scientific computing workloads. |
| 34 | + |
| 35 | +## Why this matters |
| 36 | + |
| 37 | +Adding `lfoss/2025b` to the EESSI RISC-V stack provides several benefits: |
| 38 | + |
| 39 | ++ access to a modern LLVM/Clang-based compiler environment on RISC-V; |
| 40 | ++ broader compiler coverage for portability testing; |
| 41 | ++ improved support for projects already using LLVM toolchains; |
| 42 | ++ additional opportunities to validate and improve RISC-V support in HPC software |
| 43 | +ecosystems. |
| 44 | + |
| 45 | +This also helps align the RISC-V stack more closely with the software offerings already |
| 46 | +available on x86\_64 and AArch64 platforms in EESSI. |
| 47 | + |
| 48 | +## Accessing the RISC-V stack |
| 49 | + |
| 50 | +The RISC-V stack is currently provided through the dedicated RISC-V development |
| 51 | +repository. To access it, make sure that the `software.eessi.io` and `dev.eessi.io` CernVM-FS repositories are available on your system, and then just run: |
| 52 | + |
| 53 | +``` |
| 54 | +$ export EESSI_VERSION_OVERRIDE=2025.06-001 |
| 55 | +$ source /cvmfs/software.eessi.io/versions/2025.06/init/lmod/bash |
| 56 | +This EESSI production version only provides a RISC-V compatibility layer, |
| 57 | +software installations are provided by the EESSI development repository at /cvmfs/dev.eessi.io/riscv. |
| 58 | +
|
| 59 | +Module for EESSI/2025.06 loaded successfully |
| 60 | +EESSI has selected riscv64/generic as the compatible CPU target for EESSI/2025.06 |
| 61 | +EESSI did not identify an accelerator on the system |
| 62 | +(for debug information when loading the EESSI module, set the environment variable EESSI_MODULE_DEBUG_INIT) |
| 63 | +``` |
| 64 | + |
| 65 | +On a RISC-V system, this will initialize the RISC-V software stack environment. |
| 66 | + |
| 67 | +You can then verify that the new toolchain is available: |
| 68 | + |
| 69 | +``` |
| 70 | +module avail lfoss |
| 71 | +``` |
| 72 | + |
| 73 | +and load it via: |
| 74 | + |
| 75 | +``` |
| 76 | +module load lfoss/2025b |
| 77 | +``` |
| 78 | + |
| 79 | +## Availability in `dev.eessi.io/riscv` |
| 80 | + |
| 81 | +The RISC-V stack is currently hosted in the EESSI development infrastructure, which is |
| 82 | +intended for pre-release and experimental software deployments. |
| 83 | + |
| 84 | +As with the rest of the RISC-V repository: |
| 85 | + |
| 86 | ++ software availability is still evolving; |
| 87 | ++ builds may be updated or replaced; |
| 88 | ++ the stack currently focuses on generic RISC-V targets. |
| 89 | + |
| 90 | +The RISC-V repository already contains a growing collection of scientific software and toolchains. |
| 91 | + |
| 92 | +## Looking ahead |
| 93 | + |
| 94 | +The addition of `lfoss/2025b` is another step toward broader and more mature RISC-V |
| 95 | +support within EESSI. |
| 96 | + |
| 97 | +Future work will include: |
| 98 | + |
| 99 | ++ expanding software coverage built with LLVM-based toolchains; |
| 100 | ++ improving validation and CI coverage for RISC-V; |
| 101 | ++ enabling additional optimized RISC-V targets as the ecosystem matures; |
| 102 | ++ continuing collaboration with the broader RISC-V and HPC communities. |
| 103 | + |
| 104 | +RISC-V remains an exciting and rapidly developing architecture for HPC and scientific |
| 105 | +computing, and EESSI aims to make portable, reproducible software stacks readily |
| 106 | +available for emerging platforms. |
| 107 | + |
| 108 | +## Learn more |
| 109 | + |
| 110 | ++ [EESSI RISC-V repository documentation](https://www.eessi.io/docs/repositories/dev.eessi.io-riscv/) |
| 111 | ++ [dev.eessi.io documentation](https://www.eessi.io/docs/repositories/dev.eessi.io/) |
| 112 | ++ [Available software in EESSI](https://www.eessi.io/docs/available_software/) |
| 113 | ++ [foss toolchain documentation](https://www.eessi.io/docs/available_software/detail/foss) |
| 114 | + |
0 commit comments