Pete Cooper aaa3fa61d2 Rename NumOperands to make it clear its managed by the User. NFC. ... This is to try make it very clear that subclasses shouldn't be changing the value directly. Now that OperandList for normal instructions is computed using the NumOperands, its critical that the NumOperands is accurate or we could compute the wrong offset to the first operand. I looked over all places which update NumOperands and they are all safe. Hung off use User's don't use NumOperands to compute the OperandList so they are safe to continue to manipulate it. The only other User which changed it was GlobalVariable which has an optional init list but always allocated space for a single Use. It was correctly setting NumOperands to 1 before setting an initializer, and setting it to 0 after clearing the init list, so the order was safe. Added some comments to that code to make sure that this isn't changed in future without being aware of this constraint. Reviewed by Duncan Exon Smith. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@239621 91177308-0d34-0410-b5e6-96231b3b80d8		2015-06-12 17:48:10 +00:00
..
llvm	Rename NumOperands to make it clear its managed by the User. NFC.	2015-06-12 17:48:10 +00:00
llvm-c	LTO: expose LTO_SYMBOL_COMDAT flag, which indicates that the definition is part of a comdat group.	2015-06-11 21:41:27 +00:00