We also have IsRV64 which, unless I'm missing something, contains the same information. I did add an assert to catch the case where the triple and cpu are out of sync. I haven't checked, but I assume a more useful error is reported by clang. Or at least, I can't think of a configuration where a rv32 triple and a rv64 cpu definition (and thus ISEL) make sense. Posting this for review mostly to make sure I'm not missing something on that point.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
There's a CPU check in llvm/lib/Target/RISCV/MCTargetDesc//RISCVBaseInfo.cpp in the validate function