search for: instructionval

...ing bug 122. 00134 /// getValueType - Return an ID for the concrete type of this object. This is 00135 /// used to implement the classof checks. This should not be used for any 00136 /// other purpose, as the values may change as LLVM evolves. Also, note that 00137 /// starting with the InstructionVal value, the value stored is actually the 00138 /// Instruction opcode, so there are more than just these values possible here 00139 /// (and Instruction must be last). 00140 /// 00141 enum ValueTy { 00142 ArgumentVal, // This is an instance of Argument 00143 BasicBlockVa...

...--------------------------------------------------------- BasicBlock::iterator it; ... for(int k=0; k<OpNum; k++){ errs()<<it->getOperand(k)<<" "; } ... // -------------------------------------------------------------------- Also I try it->getVaueID(), and it->InstructionVal to get destination operand. They don't work and I know what they return now ). <ofv at wanadoo.es>(My computer can't display your name correctly, and I am sorry for this.) is right, getOperand() actually returns Value*. The reason that I see string like '0x9063489' is that...

...... > for(int k=0; k<OpNum; k++){ > errs()<<it->getOperand(k)<<" "; try this: it->getOperand(k)->dump() > } > ... > // -------------------------------------------------------------------- > > Also I try > it->getVaueID(), and it->InstructionVal > to get destination operand. What do you mean by "destination operand"? Ciao, Duncan.

Launcher <st.liucheng at gmail.com> writes: > I am able to access the source operands of an instruction using either > getOperand() or op_iterator, However, I can't find any method available for > destination operand. Someone suggests that instruction itself can represent > the destination operand. > http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-January/037518.html

I am able to access the source operands of an instruction using either getOperand() or op_iterator, However, I can't find any method available for destination operand. Someone suggests that instruction itself can represent the destination operand. http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-January/037518.html The getOperand() returns an unsigned value like 0x9063498, while I can't