similar to: how to add the location debug info for each instruction

> 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

I want to insert new alloca Instruction after existing alloca Instruction in llvm pass so what attribute to be passed at last in following newallocaI = new AllocaInst(llvm::Type::getInt32PtrTy(context,0), //type 0, // ArraySize 8, // Alignment

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

> 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 >

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

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 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

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, Do you know where I can find the correct metadata layout in the source code package (which file)? I found a source code that used llvm 2.5 following a slightly different metadata layout as what I read on http://llvm.org/docs/SourceLevelDebugging.html#debugger-intrinsic-functions, which should be compatible with the latest 3.6 version, so where can I check the detailed difference in each

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, 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, 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 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

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():

Hi Philip, Thank you very much for your answer, the vector declaration example worked. I'm pretty sure the ValueToValueMapTy is the last thing I need because I even saw there is another function that could help me llvm*:*:RemapFunction <http://llvm.org/doxygen/namespacellvm.html#addf0183e92893bdbcde00fc9091dda93>; but my problem is that I don't know how to populate the

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!

Hi, I need to pass some arguments to CreateCall function (as Value *). For example, I need to pass a 64 bit integer (with a value I calculate). How can I convert the 64 bit integer to a value * in order to pass it? Thanks a lot, Tehila. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Philip, Thanks for the reference, I was able to follow it and copy the code that I saw necessary, but I still have some issues (references are still not updated). I created the function: void populateVMap(llvm::ValueToValueMapTy &VMap, llvm::Function *fOld, llvm::Function *fNew) { llvm::Function::arg_iterator DestI = fOld->arg_begin(); for (llvm::Function::const_arg_iterator J =