[all-commits] [llvm/llvm-project] e4e8ea: [RISCV] Don't require specific extensions to use a...
Craig Topper via All-commits
all-commits at lists.llvm.org
Mon Jun 8 21:35:30 PDT 2026
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: e4e8ea4c913bbf253cbab2dbcb29d3500a5689ac
https://github.com/llvm/llvm-project/commit/e4e8ea4c913bbf253cbab2dbcb29d3500a5689ac
Author: Craig Topper <craig.topper at sifive.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M llvm/lib/Target/RISCV/AsmParser/RISCVAsmParser.cpp
M llvm/lib/Target/RISCV/MCTargetDesc/RISCVInstPrinter.cpp
M llvm/test/MC/RISCV/rvv/invalid.s
M llvm/test/MC/RISCV/rvv/vsetvl-alt.s
M llvm/test/MC/RISCV/rvv/vsetvl-invalid.s
M llvm/test/MC/RISCV/rvv/zvfbdota32f-invalid.s
Log Message:
-----------
[RISCV] Don't require specific extensions to use altfmt with vset(i)vli. (#202458)
The list of extensions that use altfmt is increasing and is becoming
unsustainable. The likelihood of the bit being repurposed is decreasing
with each new use. Let's just allow it unconditionally.
There is some risk here since all of these extensions are still
unratified and experimental so it could be that all of these extensions
get redefined so that this bit doesn't become altfmt. But I think that's
unlikely.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list