search for: isinvariant

...getDebugLoc(), > dupVal.getOperand(0), dupVal.getOperand(1), > dupNode->getPointerInfo(), > dupNode->isVolatile(), dupNode->isNonTemporal(), > dupNode->isInvariant(), dupNode->getAlignment(), > dupNode->getTBAAInfo(), dupNode->getRanges()); > However, my problem now is that it will re-use the same load still. If I change something, like setting volatile to true for example, it will create a new node, but otherwis...

...ValueType(), dupVal.getDebugLoc(), dupVal.getOperand(0), dupVal.getOperand(1), dupNode->getPointerInfo(), dupNode->isVolatile(), dupNode->isNonTemporal(), dupNode->isInvariant(), dupNode->getAlignment(), dupNode->getTBAAInfo(), dupNode->getRanges()); However, my problem now is that it will re-use the same load still. If I change something, like setting volatile to true for example, it will create a new node, but otherwise it will...

...ic arguments). It may also be possible to use an intrinsic to mark the pointer itself instead of the instructions manipulating it, again it depends on what you are modelling. I've found that in the DAGBuilder metadata information connected with > LoadInst instruction is utilized: > bool isInvariant = I.getMetadata(LLVMContext::MD_invariant_load) != > nullptr; > > Is this metadata somehow protected against dropping - as you mentioned? > Nothing is protected as far as I know, the design is that it should always be legal to drop a metadata. I don’t know what the invariant_load infor...

Hi, I am writing an llvm target and I need both loads for isel reasons, but I am struggling to find the right way. I have been trying to use DAG.getLoad() to make a copy, then just change the operand in the consumers, but I cannot seem to get all of the arguments needed for that function in order to make the copy. Any help would be great, thanks! -Joe -------------- next part -------------- An

...dupVal.getOperand(0), > dupVal.getOperand(1), > > dupNode->getPointerInfo(), > > dupNode->isVolatile(), > dupNode->isNonTemporal(), > > dupNode->isInvariant(), > dupNode->getAlignment(), > > dupNode->getTBAAInfo(), > dupNode->getRanges()); > > However, my problem now is that it will re-use the same load still. If > I change something, like setting volatile to true for example, it will > c...

...al.getOperand(0), >> > dupVal.getOperand(1), >> > dupNode->getPointerInfo(), >> > dupNode->isVolatile(), >> > dupNode->isNonTemporal(), >> > dupNode->isInvariant(), >> > dupNode->getAlignment(), >> > dupNode->getTBAAInfo(), >> > dupNode->getRanges()); >> > However, my problem now is that it will re-use the same load still. If >> > I change something, like setting volatile...

...al.getOperand(1), >> >> > dupNode->getPointerInfo(), >> >> > dupNode->isVolatile(), >> >> > dupNode->isNonTemporal(), >> >> > dupNode->isInvariant(), >> >> > dupNode->getAlignment(), >> >> > dupNode->getTBAAInfo(), >> >> > dupNode->getRanges()); >> >> > However, my problem now is that it will re-use the same load still. >> >> > I...

...t;> > dupVal.getOperand(1), > >> > dupNode->getPointerInfo(), > >> > dupNode->isVolatile(), > >> > dupNode->isNonTemporal(), > >> > dupNode->isInvariant(), > >> > dupNode->getAlignment(), > >> > dupNode->getTBAAInfo(), > >> > dupNode->getRanges()); > >> > However, my problem now is that it will re-use the same load still. > If > >> > I change som...

...t; >> >> > dupNode->getPointerInfo(), > >> >> > dupNode->isVolatile(), > >> >> > dupNode->isNonTemporal(), > >> >> > dupNode->isInvariant(), > >> >> > dupNode->getAlignment(), > >> >> > dupNode->getTBAAInfo(), > >> >> > dupNode->getRanges()); > >> >> > However, my problem now is that it will re-use the same load still. >...

On Tue, Apr 30, 2019 at 3:51 PM Przemyslaw Ossowski via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > as I wrote in mu previous post I wanted to somehow mark one IR instruction > (in this particular case it would be 'load') during dedicated pass, which > will set the marking based on neighboring instructions. Next I wanted to > somehow to convey this marking

Hello, I've hit an assertion in SelectionDAG where we try to merge 2 loads that have the same operands but their MMO flags differ. One is dereferenceable and one is not. I'm not sure what the underlying issue here is: 1) MDSDNode with the same operands should have the same flags set on their respective MMO. The fact the flags differ when the opcode,types,operands and address-space are

...ddr = DAG.getLoad(PtrVT, dl, DAG.getEntryNode(), PoolAddr, + MachinePointerInfo::getConstantPool(), + /*isVolatile=*/ false, + /*isNonTemporal=*/ true, + /*isInvariant=*/ true, 8); + if (GN->getOffset() != 0) + return DAG.getNode(ISD::ADD, dl, PtrVT, GlobalAddr, + DAG.getConstant(GN->getOffset(), PtrVT)); + + return GlobalAddr; + } + + if (Alignment == 0) { + const PointerType *GVPtrTy = cast<PointerType>(GV-&gt...

...4,7 @@ public: /// Abstact virtual class for operations for memory operations class MemSDNode : public SDNode { private: + // MemoryVT - VT of in-memory value. EVT MemoryVT; @@ -1013,9 +1014,11 @@ public: bool isNonTemporal() const { return (SubclassData >> 6) & 1; } bool isInvariant() const { return (SubclassData >> 7) & 1; } + AtomicOrdering getOrdering() const { return AtomicOrdering((SubclassData >> 8) & 15); } + SynchronizationScope getSynchScope() const { return SynchronizationScope((SubclassData >> 12) & 1); } @@ -108...