replica
/
hanchenye-llvm-project
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Document the use of getValueType() more accurately, specifically explain 

that the instruction opcode is added to the InstructionVal value and the
consequences of that.

llvm-svn: 34937
This commit is contained in:
Reid Spencer 2007-03-05 23:06:32 +00:00
parent ec2b9a7850
commit ad0075d6d4
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
llvm/include/llvm/Value.h
View File

@ -181,10 +181,12 @@ public:
/// getValueType - Return an ID for the concrete type of this object. This is
/// used to implement the classof checks. This should not be used for any
/// other purpose, as the values may change as LLVM evolves. Also, note that
/// starting with the InstructionVal value, the value stored is actually the
/// Instruction opcode, so there are more than just these values possible here
/// (and Instruction must be last).
///
/// for instructions, the Instruction's opcode is added to InstructionVal. So
/// this means three things:
/// # there is no value with code InstructionVal (no opcode==0).
/// # there are more possible values for the value type than in ValueTy enum.
/// # the InstructionVal enumerator must be the highest valued enumerator in
/// the ValueTy enum.
unsigned getValueType() const {
return SubclassID;
}