similar to: [LLVMdev] How to get the debug information for an LLVM IR type?

Hi, I am now trying to do some code analysis and need to get the debug information of the LLVM IR type encountered in the bitcode. In detail, given a LLVM Type object, is it possible for me to retrieve the corresponding DIType (or MDNode) object? I feel LLVM should be able to know everything about a type, if the source file is compiled with the -g option by clang. I tried various methods but

On Mon, Jul 21, 2014 at 3:48 PM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Mon, Jul 21, 2014 at 3:41 PM, David Blaikie <dblaikie at gmail.com> wrote: >> >> On Mon, Jul 21, 2014 at 3:35 PM, Manman Ren <manman.ren at gmail.com> wrote: >> > >> > >> > >> > On Mon, Jul 21, 2014 at 1:14 PM, David Blaikie

Hi Ben, Thanks that helped a lot. The problem seems to be that with the move to C++11 we now have: void std::vector<_Ty>::push_back(std::pair<_Ty1,_Ty2> &&)' and there no conversion operator that can be applied to convert: 'std::pair<_Ty1,_Ty2>' to 'std::pair<_Ty3,_Ty4> && Where: [ _Ty1=void *,

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 =

First cleanup patch: r185020 Let me know if you have questions. Thanks, Manman On Jun 25, 2013, at 3:56 PM, Eric Christopher wrote: >>> Those parts of the codebase actually trying to handle debug info >>> should be handling valid debug info to begin with - we shouldn't need >>> to call "Verify" all over the place & behave differently (at most it

On Mon, Jul 21, 2014 at 3:35 PM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Mon, Jul 21, 2014 at 1:14 PM, David Blaikie <dblaikie at gmail.com> wrote: >> >> On Mon, Jul 21, 2014 at 10:39 AM, Manman Ren <manman.ren at gmail.com> wrote: >> > >> > >> > >> > On Mon, Jul 14, 2014 at 11:32 AM, Manman Ren

Hi, I'm currently porting some code from LLVM 2.6 to 2.8 and need to be able to extract the debug info produced by LLVM-GCC and stored in the compiled .bc file. However I admit I'm slightly confused about how exactly to do that, the documentation doesn't seem to be very clear about this, it mainly describes how to *generate* debug info. Specifically I'm wondering about the

On Jan 4, 2011, at 7:32 PM, Jacob Zimmermann wrote: > Hi, > > I'm currently porting some code from LLVM 2.6 to 2.8 and need to be able > to extract the debug info produced by LLVM-GCC and stored in the > compiled .bc file. However I admit I'm slightly confused about how > exactly to do that, the documentation doesn't seem to be very clear > about this, it mainly

On Thu, 2011-01-06 at 11:13 -0800, Devang Patel wrote: > On Jan 4, 2011, at 7:32 PM, Jacob Zimmermann wrote: > > > Hi, > > > > I'm currently porting some code from LLVM 2.6 to 2.8 and need to be able > > to extract the debug info produced by LLVM-GCC and stored in the > > compiled .bc file. However I admit I'm slightly confused about how > >

On Jun 25, 2013, at 11:35 AM, David Blaikie wrote: > On Tue, Jun 25, 2013 at 10:13 AM, Manman Ren <mren at apple.com> wrote: >> >> On Jun 25, 2013, at 9:15 AM, David Blaikie <dblaikie at gmail.com> wrote: >> >> On Tue, Jun 25, 2013 at 8:59 AM, Manman Ren <mren at apple.com> wrote: >> >> >> Any suggestion on how to move this

On Jun 25, 2013, at 9:15 AM, David Blaikie <dblaikie at gmail.com> wrote: > On Tue, Jun 25, 2013 at 8:59 AM, Manman Ren <mren at apple.com> wrote: >> > >> Any suggestion on how to move this forward? >> My feeling is that we should not call Verify from so many files. >> If you agree, I can try to clean up the Verify functions first. > > Yes, we

Some scoping for option a: There are a few Verify functions DISubprogram::Verify DICompositeType::Verify DIType::Verify that try to access the context link: if (getContext() && !getContext().Verify()) return false; And the Verify functions are called from 10+ files. If we are oaky with not calling getContext().Verify(), option a) appears much better to me. For printing | debugging

On Mon, Jul 21, 2014 at 10:39 AM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Mon, Jul 14, 2014 at 11:32 AM, Manman Ren <manman.ren at gmail.com> wrote: >> >> >> We still have access to types via MDNodes directly and the assertion that >> assumes all accesses to DITypes are accessing the resolved DIType will fire >> >> i.e

On 07/27/2015 10:59 AM, Rodney M. Bates wrote: > > > On 07/25/2015 08:57 PM, Andrew Wilkins wrote: >> On Sun, 26 Jul 2015 at 06:48 Rodney M. Bates <rodney_bates at lcwb.coop <mailto:rodney_bates at lcwb.coop>> wrote: >> >> In trying to write a C binding for DIBuilder of llvm 3.6.1, I can't see a way to unwrap >> llvm::DITypeRef, declared in

>>> Would the right starting point be to simply add an MDNode pointer to the Type class? That should be then convertible to a DIType? >> >> We want to avoid any Type class modification. Instead you can use pair in named metadata to match metadata with type. >> >> !11 = metadata !{i32 524307, metadata !1, metadata !"T", metadata !1, i32 2, i64 32, i64

Hello, I'm having this error and couldn't find a resolution from online, any help would be greatly appreciated: clang: /export/home/hzhang86/chapel/chapel-llvm36/chapel/third-party/llvm/llvm/lib/CodeGen/AsmPrinter/DwarfUnit.cpp:839: void llvm::DwarfUnit::addType(llvm::DIE&, llvm::DIType, llvm::dwarf::Attribute): Assertion `Ty && "Trying to add a type that doesn't

I think this is https://llvm.org/bugs/show_bug.cgi?id=16846 On Jun 4, 2015 12:04 PM, "Hui Zhang" <wayne.huizhang at gmail.com> wrote: > Is there any clue for this error ? > > Thanks > > On Tue, Jun 2, 2015 at 5:47 PM, Hui Zhang <wayne.huizhang at gmail.com> > wrote: > >> Hello, >> >> I'm having this error and couldn't find a

On Mon, Nov 18, 2013 at 11:06 AM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Mon, Nov 18, 2013 at 10:55 AM, Eric Christopher <echristo at gmail.com> > wrote: >> >> On Sun, Nov 17, 2013 at 6:35 PM, Manman Ren <manman.ren at gmail.com> wrote: >> > Hi Bill, >> > >> > Thanks for the testing case. Most of the time is

We still have access to types via MDNodes directly and the assertion that assumes all accesses to DITypes are accessing the resolved DIType will fire i.e assert(Ty == resolve(Ty.getRef())) One example is the access to DIType via DIArray in SubroutineType. If all elements in the type array are DITypes we can create a DITypeArray and use that for SubroutineType's type array instead. But we

Upgrade clang? I can't reproduce it with trunk. On 4 June 2015 at 14:48, Hui Zhang <wayne.huizhang at gmail.com> wrote: > Yes, I found this link, but what's the solution?? > > On Thu, Jun 4, 2015 at 1:09 PM, Rafael Espíndola > <rafael.espindola at gmail.com> wrote: >> >> I think this is https://llvm.org/bugs/show_bug.cgi?id=16846 >> >> On