search for: unaryinstruct

Hi I just had some code which filtered via isa<UnaryInstruction>. Strangely enough not only the instructions which inherited UnaryInstructions but also: GetElemPtrInst, SwitchInst , xor, shl where true on isa<UnaryInstruction>. While the first two seem to be at least semantically ok the latter seem somehow wrong? I didn't find the place wher...

On Dec 7, 2007, at 9:44 AM, ST wrote: > Hi > > I just had some code which filtered via isa<UnaryInstruction>. > Strangely > enough not only the instructions which inherited UnaryInstructions > but also: > GetElemPtrInst, SwitchInst , xor, shl > where true on isa<UnaryInstruction>. While the first two seem to be > at least > semantically ok the latter seem somehow wr...

...ernel_sigreturn + 0 3 opt 0x086d4198 llvm::LeakDetector::addGarbageObject(llvm::Value const*) + 29 4 opt 0x0872945f llvm::Instruction::Instruction(llvm::Type const*, unsigned int, llvm::Use*, unsigned int, llvm::Instruction*) + 109 5 opt 0x083d208b llvm::UnaryInstruction::UnaryInstruction(llvm::Type const*, unsigned int, llvm::Value*, llvm::Instruction*) + 75 6 opt 0x0873e46b llvm::CastInst::CastInst(llvm::Type const*, unsigned int, llvm::Value*, llvm::Twine const&, llvm::Instruction*) + 57 7 opt 0x0873124d llvm::BitCastInst::Bi...

...) [with X = llvm::PointerType, Y = const llvm::Type*]: Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed." This is because LoadInst is implemented as: LoadInst::LoadInst(Value *Ptr, const Twine &Name, BasicBlock *InsertAE) : UnaryInstruction(cast<PointerType>(Ptr->getType())->getElementType(), Load, Ptr, InsertAE) { ... } and pb->getType() is not a "PointerType"!!! WHY? Is it because it is a function call? In this situation, how can I load %2 assuming it has been load before. Can any...

Hi all, I'm having a bit of trouble with the online doxygen documentation. As far is I know, it should reflect current svn trunk. However, it seems out of date. For example, the ExtractValueInst [1] is not a UnaryInstruction yet and still takes Value* as indices. To add to the confusing, the mainpage [2] says it is documentation version "2.1svn" which seems even more weird. What gives? Matthijs [1]: http://www.llvm.org/doxygen/classllvm_1_1ExtractValueInst.html [2]: http://www.llvm.org/doxygen/ -------...

...ing results in: libqdp.a(qdp_llvm.o):(.rodata._ZTIN4llvm8FCmpInstE[_ZTIN4llvm8FCmpInstE]+0x10): undefined reference to `typeinfo for llvm::CmpInst' libqdp.a(qdp_jit_util.o):(.rodata._ZTIN4llvm16ExtractValueInstE[_ZTIN4llvm16ExtractValueInstE]+0x10): undefined reference to `typeinfo for llvm::UnaryInstruction' libqdp.a(qdp_jit_util.o):(.rodata._ZTIN4llvm15InsertValueInstE[_ZTIN4llvm15InsertValueInstE]+0x10): undefined reference to `typeinfo for llvm::Instruction' collect2: error: ld returned 1 exit status I searched for this and there seem to be two common causes for this 1) There are vir...

...= > const llvm::Type*]: Assertion `isa<X>(Val) && "cast<Ty>() argument of > incompatible type!"' failed." > > This is because LoadInst is implemented as: > > LoadInst::LoadInst(Value *Ptr, const Twine &Name, BasicBlock *InsertAE) > : UnaryInstruction(cast<PointerType>(Ptr->getType())->getElementType(), > Load, Ptr, InsertAE) > { > ... > } > > and pb->getType() is not a "PointerType"!!! WHY? Is it because it is a > function call? In this situation, how can I load %2 assuming...

...ptional) operand 2 for store. This involves changing the 'operator new' to always allocate for 2(load)/3(store) operands. Also OperandTraits of StoreInst must be modfied as we now have an optional operand. For the LoadInst, we also need to introduce an OperandTraits, to overrule the 'UnaryInstruction' one. 4) Introduce a StoreWithSideChannelInst/LoadWithSideChannelInst that inherits from StoreInst/LoadInst, together with its appropriate OperandTraits. This makes it harder to add/remove sidechannel information. Thanks, Jeroen Dobbelaere

> I'm having a bit of trouble with the online doxygen documentation. As far is I > know, it should reflect current svn trunk. However, it seems out of date. For > example, the ExtractValueInst [1] is not a UnaryInstruction yet and still > takes Value* as indices. > > To add to the confusing, the mainpage [2] says it is documentation version > "2.1svn" which seems even more weird. > > What gives? Both of these issues are fixed. It will be regenerated tonight. A lot of this stuff is aut...

On Apr 16, 2008, at 2:50 AM, heisenbug wrote: > > And now here is my educated speculation: > There are 2 things that became slower > 1) Use::getUser() > 2) Use::get/set due to tagging. > > The former is seldom called: > > $ find lib -name "*.cpp" | xargs grep "getUser(" | wc -l > 41 The majority of those aren't actually Use::getUser, but

On Apr 16, 2:13 am, Dan Gohman <goh... at apple.com> wrote: > Hi Gabor, > > Can you provide performance data for this? I'd > like to know what affect these changes have on > compile time. Hi Dan, Unfortunately, no. I can feed you with some speculation, though, see below. The reason why I cannot do measurements (at the moment) is that - I have no experience with