[all-commits] [llvm/llvm-project] 95d3fd: [RISCV] Refactor how we create separate instructio...
Craig Topper via All-commits
all-commits at lists.llvm.org
Fri Jun 16 11:23:16 PDT 2023
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 95d3fd9a91376e0ef60c4e7599b4d224ac6f0e6f
https://github.com/llvm/llvm-project/commit/95d3fd9a91376e0ef60c4e7599b4d224ac6f0e6f
Author: Craig Topper <craig.topper at sifive.com>
Date: 2023-06-16 (Fri, 16 Jun 2023)
Changed paths:
M llvm/lib/Target/RISCV/RISCVInstrInfoD.td
M llvm/lib/Target/RISCV/RISCVInstrInfoF.td
M llvm/lib/Target/RISCV/RISCVInstrInfoZfh.td
Log Message:
-----------
[RISCV] Refactor how we create separate instructions for F and Zfinx. NFC
Previously we had a ExtInfo_rr class that was instantiated for
every combination of types that can appear together along with
their predicates, suffixes, and decoder namespace.
This patch replaces this with a new ExtInfo class that contains
predicates, suffix, namespace, and the f16, f32, and f64 DAGOperands
implied by the predicates. The DAGOperand can be unset if
the predicate is not enough to distinquish it.
At every instruction instantiation we know whether the operands
are GPR, f16, f32, or f64 and can ask the ExtInfo for the relevant
DAGOperand.
The foreach loops of ExtInfo have been moved out of the classes to
be at the top level of the 3 files. This allows the file to pick
the f16/f32/f64 DAGOperand per instruction and pass it down to the
classes separately from the ExtInfo. The ExtInfo still needs to be
passed down to get suffix, predicates, and decoder namespace.
Reviewed By: sunshaoce
Differential Revision: https://reviews.llvm.org/D152948
More information about the All-commits
mailing list