[GISel]: Don't assert when constraining RegisterOperands which are uses.
authorAditya Nandakumar <aditya_nandakumar@apple.com>
Mon, 26 Feb 2018 22:56:21 +0000 (22:56 +0000)
committerAditya Nandakumar <aditya_nandakumar@apple.com>
Mon, 26 Feb 2018 22:56:21 +0000 (22:56 +0000)
commit599990530efd0985bb67d6659db7a2d32ccbb1c3
treeab3f0879b711794c2c64e23736b23d85be36fcf2
parent54af3e7e142684144daf1a1387351a46053f821d
[GISel]: Don't assert when constraining RegisterOperands which are uses.

Currently we assert that only non target specific opcodes can have
missing RegisterClass constraints in the MCDesc. The backend can have
instructions with register operands but don't have RegisterClass
constraints (say using unknown_class) in which case the instruction
defining the register will constrain it.
Change the assert to only fire if a def has no regclass.

https://reviews.llvm.org/D43409

llvm-svn: 326142
llvm/include/llvm/CodeGen/GlobalISel/Utils.h
llvm/lib/CodeGen/GlobalISel/Utils.cpp
llvm/lib/Target/AArch64/AArch64CallLowering.cpp
llvm/lib/Target/ARM/ARMCallLowering.cpp
llvm/lib/Target/X86/X86CallLowering.cpp