Evan Cheng 8d3af5e7d0 Instructions with variable operands (variable_ops) can have a number required ... operands. e.g. def CALL32r : I<0xFF, MRM2r, (ops GR32:$dst, variable_ops), "call {*}$dst", [(X86call GR32:$dst)]>; TableGen should emit operand informations for the "required" operands. Added a target instruction info flag M_VARIABLE_OPS to indicate the target instruction may have more operands in addition to the minimum required operands. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@28791 91177308-0d34-0410-b5e6-96231b3b80d8		2006-06-15 07:22:16 +00:00
..
MRegisterInfo.h	Also add super- register class info.	2006-05-11 07:31:44 +00:00
SubtargetFeature.h
TargetData.h	Make TargetData strings less redundant.	2006-05-20 23:28:54 +00:00
TargetFrameInfo.h
TargetInstrInfo.h	Instructions with variable operands (variable_ops) can have a number required	2006-06-15 07:22:16 +00:00
TargetInstrItineraries.h
TargetJITInfo.h
TargetLowering.h	Start on my todo list	2006-06-12 16:07:18 +00:00
TargetMachine.h	Refactor a bunch of includes so that TargetMachine.h doesn't have to include	2006-05-12 06:33:49 +00:00
TargetMachineRegistry.h	Improve comments, patch provided by Vladimir Prus!	2006-05-15 17:25:05 +00:00
TargetOptions.h	-enable-unsafe-fp-math implies -enable-finite-only-fp-math	2006-05-23 18:18:46 +00:00
TargetSubtarget.h