llvm/llvm-project

[RISC-V] Update Linux Feature Detection

Open

#192317 opened on Apr 15, 2026

View on GitHub
 (9 comments) (1 reaction) (1 assignee)C++ (26,378 stars) (10,782 forks)batch import
backend:RISC-Vgood first issue

Description

There are new architecture hwprobe features exposed by recent linux versions. The docs are here: https://docs.kernel.org/arch/riscv/hwprobe.html

I think we have implemented up to RISCV_HWPROBE_EXT_ZAWRS, but no further. We should add support for the rest of the supported extensions.

This entails:

  • Proposing extension bitmask assignments for (standard) extensions that don't have them already. This is done via the https://github.com/riscv-non-isa/riscv-c-api-doc repo (note that there are some proposed but not yet landed bitmask assignments in the open PRs for that repo, which new proposals should not conflict with).
  • Add the RISCVExtensionBitmask to the relevant extensions.
  • Implement detection in llvm/lib/TargetParser/Host.cpp (used by -march=native) and compiler-rt/lib/builtins/cpu_model/riscv.c (used by ifuncs)

There is no compiler-rt interface for exposing vendor-specific extensions (which have a different hwprobe keys), but we may still be able to detect them in llvm/lib/TargetParser/Host.cpp for -march=native.

This would also be a good opportunity to move away from the deprecated RISCV_HWPROBE_KEY_CPUPERF_0, and to RISCV_HWPROBE_KEY_MISALIGNED_SCALAR_PERF, and also implement the same for RISCV_HWPROBE_KEY_MISALIGNED_VECTOR_PERF potentially (this can be a separate PR).

Contributor guide

Tech stack
cpp
Domain
backendtoolingperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
RISC V architectureLLVM developmentC++Linux hwprobe
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Start by reviewing the Linux kernel docs for new hwprobe features and existing bitmask assignments in the riscv c api doc repo. Examine open PRs in that repo to avoid conflicts. Then, follow the pattern in llvm/lib/TargetParser/Host.cpp and compiler rt/lib/builtins/cpu model/riscv.c to add detection for new extensions. Consider also migrating from deprecated RISCV HWPROBE KEY CPUPERF 0 to the new key, but that could be a separate PR.