mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-19 19:12:56 +02:00
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:
parent
79495d839e
commit
5ecf7f6214
@ -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;
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user