search for: weakvh

I'm probably missing something simple here but in: CGDebugInfo.h: std::vector<std::pair<void *, llvm::WeakVH> >ReplaceMap; but then in CGDebugInfo.cpp: llvm::DIType TC = getTypeOrNull(Ty); void * v = Ty.getAsOpaquePtr(); std::pair<void *, llvm::WeakVH> tmp = std::make_pair(v, TC); if (TC.Verify() && TC.isForwardDecl()) ReplaceMap.push_back(Ty.getTypeOrNull(), TC); Not...

On 09.08.2012, at 19:43, "Gaster, Benedict" <Benedict.Gaster at amd.com> wrote: > I’m probably missing something simple here but in: > > CGDebugInfo.h: > > std::vector<std::pair<void *, llvm::WeakVH> >ReplaceMap; > > but then in > > CGDebugInfo.cpp: > > llvm::DIType TC = getTypeOrNull(Ty); > > void * v = Ty.getAsOpaquePtr(); > std::pair<void *, llvm::WeakVH> tmp = std::make_pair(v, TC); > > if (TC.Verify() && TC.isForwardDe...

...here no conversion operator that can be applied to convert: 'std::pair<_Ty1,_Ty2>' to 'std::pair<_Ty3,_Ty4> && Where: [ _Ty1=void *, _Ty2=llvm::DIType ] and [ _Ty3=void *, _Ty4=llvm::WeakVH ] The reason it gives is std::pair<_Ty1,_Ty2>' to 'std::pair<_Ty3,_Ty4>, but as you point out there is indeed a conversion operator for DITYPE to WeakVH. Putting the explicit cast to give: if (T.Verify() && T.isForwardDecl()) ReplaceMap.push_back(std::make_...

Михаил wrote: > It is ModulePass with AnalysisUsage of CallGraph Ah, then you'll need to update the CallGraph first. Use "CG.removeFunctionFromModule(F);" before deleting it. Nick > Yours sincerely, > Kadysev Mikhail > > 22.04.2012, в 5:20, Nick Lewycky написал(а): > >> Михаил wrote: >>> Thanks, but I replaceAllUsesWith() - works well, but I still

...t/lib/libLLVM-3.6svn.so > #6 0x00007ffff3a40eed in llvm::MDNode::getTemporary(llvm::LLVMContext&, llvm::ArrayRef<llvm::Metadata*>) () from /opt/buildbot/lib/libLLVM-3.6svn.so > #7 0x00007ffff3426b3f in MapValueImpl(llvm::Metadata const*, llvm::ValueMap<llvm::Value const*, llvm::WeakVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex<false> > >&, llvm::RemapFlags, llvm::ValueMapTypeRemapper*, llvm::ValueMaterializer*) () > from /opt/buildbot/lib/libLLVM-3.6svn.so > #8 0x00007ffff3426bd6 in MapValueImpl(llvm::Metadata const*, llvm::ValueM...

It is ModulePass with AnalysisUsage of CallGraph Yours sincerely, Kadysev Mikhail 22.04.2012, в 5:20, Nick Lewycky написал(а): > Михаил wrote: >> Thanks, but I replaceAllUsesWith() - works well, but I still get bug in >> eraseFromParent(): >> >> While deleting: i32 (%class.B*, i32)* %_ZN1B1xEi >> An asserting value handle still pointed to this value! >>

Hi, Here is the code in IndVarSimplify.cpp. SmallVector<WeakVH, 16> DeadInsts; while (!DeadInsts.empty()) if (Instruction *Inst = dyn_cast_or_null<Instruction>(&*DeadInsts.pop_back_val())) RecursivelyDeleteTriviallyDeadInstructions(Inst, TLI); Since DeadInsts.pop_back_val() is WeakVH which could hold a NULL pointer, the ex...

The `Metadata`/`Value` split (PR21532) landed in r223802 -- at least, the C++ side of it. This was a rocky day, but I suppose that's what I get for failing to stage the change in smaller pieces. As of r223916 (lldb), I'm not aware of any remaining (in-tree) breakage, so if I've missed some problem in the sea of buildbot errors, please flag me down. I'll follow up soon with

...6svn.so >>> #6 0x00007ffff3a40eed in llvm::MDNode::getTemporary(llvm::LLVMContext&, llvm::ArrayRef<llvm::Metadata*>) () from /opt/buildbot/lib/libLLVM-3.6svn.so >>> #7 0x00007ffff3426b3f in MapValueImpl(llvm::Metadata const*, llvm::ValueMap<llvm::Value const*, llvm::WeakVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex<false> > >&, llvm::RemapFlags, llvm::ValueMapTypeRemapper*, llvm::ValueMaterializer*) () >>> from /opt/buildbot/lib/libLLVM-3.6svn.so >>> #8 0x00007ffff3426bd6 in MapValueImpl(llvm::Metadata const...

...gt;>> #6 0x00007ffff3a40eed in llvm::MDNode::getTemporary(llvm::LLVMContext&, llvm::ArrayRef<llvm::Metadata*>) () from /opt/buildbot/lib/libLLVM-3.6svn.so > >>>> #7 0x00007ffff3426b3f in MapValueImpl(llvm::Metadata const*, llvm::ValueMap<llvm::Value const*, llvm::WeakVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex<false> > >&, llvm::RemapFlags, llvm::ValueMapTypeRemapper*, llvm::ValueMaterializer*) () > >>>> from /opt/buildbot/lib/libLLVM-3.6svn.so > >>>> #8 0x00007ffff3426bd6 in MapValueImpl(llv...

Duncan Sands wrote: > Hi Nick, > >> I'm looking for input into the syntax for future metadata work. The plan >> is to make MDNodes hold a list of WeakVHs which will allow us to track >> metadata associated with values even through calls to >> ReplaceAllUsesWith. It also means that you can refer to other Values in >> the program, including instructions in another Function. >> >> That's where the problems begin. T...

...> #6 0x00007ffff3a40eed in llvm::MDNode::getTemporary(llvm::LLVMContext&, llvm::ArrayRef<llvm::Metadata*>) () from /opt/buildbot/lib/libLLVM-3.6svn.so >>>>>>> #7 0x00007ffff3426b3f in MapValueImpl(llvm::Metadata const*, llvm::ValueMap<llvm::Value const*, llvm::WeakVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex<false> > >&, llvm::RemapFlags, llvm::ValueMapTypeRemapper*, llvm::ValueMaterializer*) () >>>>>>> from /opt/buildbot/lib/libLLVM-3.6svn.so >>>>>>> #8 0x00007ffff3426bd6 in Ma...

...toreInst doesn't overlap that StoreInst" in a > metadata. Or perhaps "here's the likely values for this SwitchInst". well... ok, if you must :) > I have only weak ideas for how interprocedural metadata could be used, > but it's clear that an MDNode made out of WeakVH's could hold one, which > is why I'd like to get a syntax for them. It's certainly something that > could wait until we have a client, but I was hoping to not make multiple > different syntaxes/bitcode formats that we would have to support in the > future. How can MDNod...

I'm looking for input into the syntax for future metadata work. The plan is to make MDNodes hold a list of WeakVHs which will allow us to track metadata associated with values even through calls to ReplaceAllUsesWith. It also means that you can refer to other Values in the program, including instructions in another Function. That's where the problems begin. There's currently no way in llvm assembl...

.../c++/v1/vector:676:36: note: candidate function not viable: no known conversion from 'pair<typename __make_pair_return<void *>::type, typename __make_pair_return<DIType &>::type>' to 'const value_type' (aka 'const std::__1::pair<void *, llvm::WeakVH>') for 1st argument; _LIBCPP_INLINE_VISIBILITY void push_back(const_reference __x); ^ /usr/include/c++/v1/vector:678:36: note: candidate function not viable: no known conversion from 'pair<typename __make_pair_return<void *>::ty...

Dear All, The LLVM 2.6 Release Branch doesn't compile for me on Mac OS X. The following patch seems to fix it (it adds a missing include file to get WeakVH defined). Has anyone else seen this breakage, or is it possible that I've got the wrong branch checked out? -- John T. Index: lib/Transforms/Scalar/DeadStoreElimination.cpp =================================================================== --- lib/Transforms/Scalar/DeadStoreElimination.cpp...

...a6ab5d llvm::InstVisitor<(anonymous namespace)::DIUpdater, void>::visit(llvm::Module*) + 29 25 lli               0x0000000101a6ab0a (anonymous namespace)::DIUpdater::DIUpdater(llvm::Module&, llvm::StringRef, llvm::StringRef, llvm::Module const*, llvm::ValueMap<llvm::Value const*, llvm::WeakVH, llvm::ValueMapConfig<llvm::Value const*> > const*) + 378 26 lli               0x0000000101a6a1ff (anonymous namespace)::DIUpdater::DIUpdater(llvm::Module&, llvm::StringRef, llvm::StringRef, llvm::Module const*, llvm::ValueMap<llvm::Value const*, llvm::WeakVH, llvm::ValueMapConfig&l...

Hi Nick, > I'm looking for input into the syntax for future metadata work. The plan > is to make MDNodes hold a list of WeakVHs which will allow us to track > metadata associated with values even through calls to > ReplaceAllUsesWith. It also means that you can refer to other Values in > the program, including instructions in another Function. > > That's where the problems begin. There's currentl...

...-yet-unknown in Metadata.h. Context.pImpl->TheMetadata.ValueIsDeleted(this); in ~Value will always call the empty ValueIsDeleted(Value*) overload. Please write a unittest for this. Metadata::getMDKind(Name) can just be "return MDHandlerNames.lookup(Name)" Could you comment what the WeakVH in MDPairTy is following? I got confused and thought it was tracking the Instruction holding the metadata rather than the MDNode. You did say this was partial; sorry if I pointed out anything you were already planning to do. Jeffrey

...a6ab5d llvm::InstVisitor<(anonymous namespace)::DIUpdater, void>::visit(llvm::Module*) + 29 25 lli 0x0000000101a6ab0a (anonymous namespace)::DIUpdater::DIUpdater(llvm::Module&, llvm::StringRef, llvm::StringRef, llvm::Module const*, llvm::ValueMap<llvm::Value const*, llvm::WeakVH, llvm::ValueMapConfig<llvm::Value const*> > const*) + 378 26 lli 0x0000000101a6a1ff (anonymous namespace)::DIUpdater::DIUpdater(llvm::Module&, llvm::StringRef, llvm::StringRef, llvm::Module const*, llvm::ValueMap<llvm::Value const*, llvm::WeakVH, llvm::ValueMapConfig&l...