SuccessChanges

Summary

  1. [mips] Print BEQZL and BNEZL pseudo instructions One of the reasons - to be compatible with GNU tools.
  2. AMDGPU: Use standalone MUBUF load patterns We already do this for the flat and DS instructions, although it is certainly uglier and more verbose. This will allow using separate pattern definitions for extload and zextload. Currently we get away with using a single PatFrag with custom predicate code to check if the extension type is a zextload or anyextload. The generic mechanism the global isel emitter understands treats these as mutually exclusive. I was considering making the pattern emitter accept zextload or sextload extensions for anyextload patterns, but in global isel, the different extending loads have distinct opcodes, and there is currently no mechanism for an opcode matcher to try multiple (and there probably is very little need for one beyond this case).
Revision 366133 by atanasyan:
[mips] Print BEQZL and BNEZL pseudo instructions

One of the reasons - to be compatible with GNU tools.
Change TypePath in RepositoryPath in Workspace
The file was modified/llvm/trunk/lib/Target/Mips/MipsInstrInfo.td (diff)llvm.src/lib/Target/Mips/MipsInstrInfo.td
The file was modified/llvm/trunk/test/MC/Mips/branch-pseudos.s (diff)llvm.src/test/MC/Mips/branch-pseudos.s
The file was modified/llvm/trunk/test/MC/Mips/macro-bcc-imm.s (diff)llvm.src/test/MC/Mips/macro-bcc-imm.s
The file was modified/llvm/trunk/test/MC/Mips/mips-jump-delay-slots.s (diff)llvm.src/test/MC/Mips/mips-jump-delay-slots.s
Revision 366132 by arsenm:
AMDGPU: Use standalone MUBUF load patterns

We already do this for the flat and DS instructions, although it is
certainly uglier and more verbose.

This will allow using separate pattern definitions for extload and
zextload. Currently we get away with using a single PatFrag with
custom predicate code to check if the extension type is a zextload or
anyextload. The generic mechanism the global isel emitter understands
treats these as mutually exclusive. I was considering making the
pattern emitter accept zextload or sextload extensions for anyextload
patterns, but in global isel, the different extending loads have
distinct opcodes, and there is currently no mechanism for an opcode
matcher to try multiple (and there probably is very little need for
one beyond this case).
Change TypePath in RepositoryPath in Workspace
The file was modified/llvm/trunk/lib/Target/AMDGPU/BUFInstructions.td (diff)llvm.src/lib/Target/AMDGPU/BUFInstructions.td