similar to: [LLVMdev] the difference of debug information descriptor between versions

> On Nov 3, 2015, at 5:00 PM, Hui Zhang <wayne.huizhang at gmail.com> wrote: > > Hello, > > I found a weird thing in llvm 3.3: > > For exactly the same MDNode *space, if I cast it to DILocation loc(space) and call loc.getFileName(), or I cast it to DIScope sco(space) and call sco.getFilename(), the return value would be different ! Totally two different files

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

Hello, I'm a little confused by the definition of metadata node: does it have to contain different types of data ? And does a named metadata have to have a string name ? I know the named metadata can only contain metadatas e.g. !3=metadata !{metadata !1, metadata !2} Does it belong to NamedMDNode or MDNode ? Thanks! -- Best regards Hui Zhang -------------- next part -------------- An

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 2015-Jun-02, at 11:14, Hui Zhang <wayne.huizhang at gmail.com> wrote: > > Any ideas ？ > > Thanks > > On Tue, Jun 2, 2015 at 12:40 PM, Hui Zhang <wayne.huizhang at gmail.com> wrote: > Hello, > > I'm having this assertion fail when I was using DIBuilder to create the debug information: > > Expected no forward declarations! > !719 >

Hello, For some reason, I have to stick on llvm 3.3 for a language compiler, I find that the location debug info is attached to each instruction using !dbg, however, I found some of that information is mis-attched and need to be changed, so I want to *know what functions(I checked all funcs in DIBuilder.h but didn't find a appropriate one) are used to attach those !dbg nodes to each

Hello, I found some source code using llvm 2.5 that has a call to Module::getTypeName(Type*), which I can't find it anymore in llvm newer than 3.3, so how can I get the name of a type(e.g a user-defined structure) if we have Type* of that ? Besides, I checked that old llvm maintains a TypeSymbolTable that enabled type name look-up, so what's the replacement and mechanism of it in the

Hello, I'm having this assertion fail when I was using DIBuilder to create the debug information: Expected no forward declarations! !719 The assertion condition is: !isa<MDNodeFwdDecl> (MD) So My questions are: 1. What is exactly the MDNodeFwdDecl ? I saw it's in the latest release 3.6.1, but I also found this link

Hello, I don't know if anyone gets familiar with the llvm Chapel front end, it's version 3.3 and comes within Chapel source package. I'm trying to parse the .bc code generated from a simple helloworld chapel program. Just run a basic Hello pass on the code (default one in the llvm source code) that prints out all the function names in the module. However, it prints a bunch of

Hello, I'm a little confused about the 3th and 4th arguments in the registration function, explained here: http://llvm.org/releases/3.3/docs/WritingAnLLVMPass.html e.g static RegisterPass<Hello> X("hello", "Hello World Pass", false /* Only looks at CFG */, false /* Analysis Pass */); "Lastly, we

Hello, I found a function call Function::isDeclaration() in llvm 2.5 (I know that's ancient...), which is useful to me, but I can't find it in the later version 3.3, nor the latest 3.7.....Therefore, is there an alternative way to check whether the function is just a declaration or a definition ? PS: I read the source code of llvm 2.5, and found isDeclaration is simply to check if the

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

Hello, Richard Thanks a lot ! On Fri, Dec 19, 2014 at 10:04 AM, RICHARD STUCKEY < richard.stuckey at virgin.net> wrote: > > Hi, Hui Zang, > > It helps to remember that at runtime a variable of a structure type has to > be allocated store, and to think about how that variable is laid out in > store. > > You must use createMemberType to create a DIType for *each*

Hello, I'm using llvm 2.5. I initially built it with GCC 4.1.2 and it completed building. But when I run it with a simple test function, it fails with the following issue: Value still in symbol table! Type = 'i32' Name = 'a' Value still in symbol table! Type = 'i32' Name = 'b' llc: ValueSymbolTable.cpp:29: llvm::ValueSymbolTable::~ValueSymbolTable():

Hello, Everyone I'm using llvm 3.6 DIBuilder module to build the debug information for Chapel language(the Chapel-llvm front end works fine). When I run the test program, I got these assertions failed: !718 Expected no forward declarations! !719 Expected no forward declarations! !720 Expected no forward declarations! !721 Expected no forward declarations! !722 All nodes should be resolved!

Hello, I'm using DIBuilder to create debugging information, I'm not clear about two things: [1] Could you help explain the meaning and the difference between"alignment" and "offset" of a type ? e.g class Actor{ int age; const char* name; } Besides, I found the denotation of createMemberType and createStructType both have "Member

Hi Josh, On Dec 4, 2011, at 9:33 PM, Josh Matthews wrote: > I'm working on generating debug information for Rust, and I'm > currently stumped on how to generate DWARF output via LLVM that will > correctly represent this (eg. when exiting from foo2(), I'd like to > see "Value returns is $1 = 5"). I'm generating debug metadata nodes > directly instead of

Thanks for your help. I took a look at http://llvm.org/docs/SourceLevelDebugging.html and it seems like this doesn't give you much in the way of line number information. If you know what source line you are interested in then you can set a breakpoint, but suppose you want to know the line number in the source code for some arbitrary bytecode instruction. In my particular case, I have a pass

On Nov 5, 2010, at 8:04 AM, Renato Golin wrote: > Hi All, > > We've been working on a wiki page to help people build debug > information in their own front-ends: > > http://wiki.llvm.org/Debug_Information > > It's definitely a work in progress, but it already has the basic > format and how to create the basic information (line, functions, > variables,

Hello, The documentation for debug information (http://llvm.org/docs/SourceLevelDebugging.html) says the structure of block descriptors metadata is: !3 = metadata !{ i32, ;; Tag = 11 + LLVMDebugVersion (DW_TAG_lexical_block) metadata,;; Reference to context descriptor i32, ;; Line number i32 ;; Column number } However, looking at the generated metadata, there are 2 extra