[llvm] [RISCV] 'Zalrsc' may permit non-base instructions (PR #165042)

Francesco Petrogalli via llvm-commits llvm-commits at lists.llvm.org
Fri Oct 24 15:54:19 PDT 2025


================
@@ -0,0 +1,1074 @@
+; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
+; RUN: llc -mtriple=riscv32 -mattr=+zalrsc -verify-machineinstrs < %s \
+; RUN:   | FileCheck -check-prefixes=RV32I-ZALRSC %s
+; RUN: llc -mtriple=riscv32 -mattr=+b,+zalrsc,+permissive-zalrsc -verify-machineinstrs < %s \
+; RUN:   | FileCheck -check-prefixes=RV32IB-ZALRSC %s
+; RUN: llc -mtriple=riscv32 -mattr=+a -verify-machineinstrs < %s \
+; RUN:   | FileCheck -check-prefixes=RV32IA %s
----------------
fpetrogalli wrote:

isn't +a already tested somewhere else? I see them being tested in atomic-rmw.ll.

If you want to keep min/max together (which I think it is a good idea), you should remove them from atomic-rmw.ll

https://github.com/llvm/llvm-project/pull/165042


More information about the llvm-commits mailing list