[RISCV][NFC] Split PseudoCALL pattern out from instruction
authorAlex Bradbury <asb@lowrisc.org>
Tue, 16 Jul 2019 03:56:45 +0000 (03:56 +0000)
committerAlex Bradbury <asb@lowrisc.org>
Tue, 16 Jul 2019 03:56:45 +0000 (03:56 +0000)
commitef8577ef98717c1c6a66293de3b2cc0f09e8c3ff
tree5ab3e8fae296c48431ebb46ad24b71f7dc15887e
parenta3c7b27419a52d612fe2cad319aafba1e226502b
[RISCV][NFC] Split PseudoCALL pattern out from instruction

Since PseudoCALL defines AsmString, it can be generated from assembly,
and so code-gen patterns should be defined separately to be consistent
with the style of the RISCV backend. Other pseudo-instructions exist
that have code-gen patterns defined directly, but these instructions are
purely for code-gen and cannot be written in assembly.

Differential Revision: https://reviews.llvm.org/D64012
Patch by James Clarke.

llvm-svn: 366174
llvm/lib/Target/RISCV/RISCVInstrInfo.td