The recent D154183 and D154195 have introduced a simpler way to specify
instruction mnemonics: by leveraging TableGen's NAME and string
processing features, the mnemonics can be automatically derived from the
respective TableGen record names. LoongArch instructions don't have
"strange" characters in their names, so this approach can be applied to
all the other instructions.
A deriveInsnMnemonic helper class, modeled after the LSX/LASX mnemonic
derivation logic, has been added, and all non-pseudo instruction formats
are converted to use it, losing their opstr/opcstr arguments in the
process.
There are minor differences that are worth mentioning though:
- The atomic instructions with implicit data barriers have an underscore (_) in their mnemonics, that will get converted to a period (.) if not specially handled. Double-underscore (__) in record names are converted to a single underscore in the resulting mnemonic; the definitions are tweaked accordingly.
- Various duplicated FP instructions need special handling, mainly because of the need to handle both FPR32 and FPR64 classes for a single hardware instruction. The substrings _xS, _xD and _64 are additionally dropped before deriving FP instructions' mnemonics.
All of these are pure refactoring, no functional change.