[llvm] [RISCV]Add support for resolving encoding conflicts among vendor specific CSRs (PR #96174)

[Craig Topper via llvm-commits]

topperc wrote:

> Maybe we can consider a separate patch that sets the variables to true for RISC-V and modifies parser/printer to use the new API. This way downstream users of RISC-V backend do not have the burden to maintain those changes. I think most downstream users have vendor/custom CSRs that have encoding conflict. Would that be acceptable?

Yes. I definitely think we should do that.

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