similar to: [LLVMdev] About debug in LLVM!!!

Do you want to debug the native executables generated by your back-end? What debug info format your native executables support? In general, this is how it works for that case. 1. clang-cc -g generates required debug info in the .bc file. 2. The backend (llc) converts that to Dwarf (or something else as desired by that back-end). 3. Native debuggers like (gdb) understands Dwarf and provide source

Hallo, LLVMdev! I have found you in LLVM Developers page (http://llvm.org/developers.cgi). First thank you for all of your work with LLVM. About: I work with the LLVM Compiler Infrastructure to implement a backend for specific processor xPEC of chip NetX (http://hilscher.com/netx.html). So C-code already possible compile to the native xPEC assembly code (works perfect! LLWM a big

Hi Artem, GDB only works with native applications. If you compile your code to a native executable with -g, then debug info should work for you. However, if you've built your own backend, then you may need to add the debug info hooks etc. If you have further questions, please email the llvmdev mailing list instead of me directly, thanks! -Chris On Jun 26, 2009, at 11:11 AM,

Hello! I am working with LLVM project to compile for specific processor (xPEC-processor from NetX chip, http://hilscher.com/ ). I have done support of this target successfully! Assembler code can be emitted with debug information. LLVM - great!) But now I am looking for generation of machine code for my target. I have seen, that "llc" has option "-filetype". It has

----- Original Message ---- > From aaronngray.lists at googlemail.com Mon Jul 27 15:14:40 2009 > From: aaronngray.lists at googlemail.com (Aaron Gray) > Date: Mon, 27 Jul 2009 21:14:40 +0100 > Subject: [LLVMdev] llc - generation of native machine code > > > On Mon, Jul 27, 2009 at 8:25 AM, Rudskyy<tema13tema at yahoo.de> wrote: > > > But now I am looking for

Hallo! I have found the LLVM-project and hope it can be useful for me in my work. There is a processor with a simple assembly code (http://hilscher.com/ xPEC- processor). The task is that I need a "translator" from C/C++ to native assembly code. And understand, that I need to write a backend specifying my target (convertion a llvm-IR code to assembly). Can you help, suggest to

Hi Rudskyy, The place to ask LLVM-related questions is llvmdev at cs.uiuc.edu -- I've cc'd the list. 2009/1/30 Rudskyy <tema13tema at yahoo.de> > I need some help in subject: "Writing an LLVM Compiler Backend"! > > There is a processor with a simple assembly code (http://hilscher.com/ xPEC- processor). I understand, that I need to convert a llvm-IR code to

On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: > I just updated from CVS, and after doing a clean rebuild I get this error: Are you sure that no conflicts prevented updating from going smoothly? How are you building (srcdir ==/!= objdir)? -Chris > /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static > member function 'static bool

I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This is on persephone. Are you not getting this error? Perhaps I should check out a fresh tree and try to compile it? Rob On Apr 7, 2006, at 11:40 AM, Chris Lattner wrote: > On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: >> I just updated from CVS, and after doing a clean rebuild I get >> this

I just updated from CVS, and after doing a clean rebuild I get this error: /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static member function 'static bool llvm::DbgInfoIntrinsic::classof (const llvm::IntrinsicInst*)': /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:77: error: 'dbg_declare' is not a member of 'llvm::Intrinsic'

On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: > I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This > is on persephone. > > Are you not getting this error? Perhaps I should check out a fresh tree and > try to compile it? Nope, I don't think anyone else is getting this error. If you could try a fresh build that would be great, I'll fire

I've done several CVS head builds today .. no problems on Linux. Reid. On Fri, 2006-04-07 at 11:53 -0500, Chris Lattner wrote: > On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: > > > I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This > > is on persephone. > > > > Are you not getting this error? Perhaps I should check out a fresh

I'm guessing the problem occurred because I hadn't updated in a while (maybe a couple of weeks?) and I had an old Intrinsics.gen file hanging around in my source directory that was getting picked up by the makefile for some reason. This is a bug, but maybe it's harmless because there's a onetime workaround (delete the file by hand) and it won't be a problem for

OK, when I copy $(SRCDIR)/include/llvm/Intrinsics.gen to $(OBJDIR)/ include/llvm/ by hand after building (and failing) once, the build succeeds. This is definitely a makefile bug. Rob On Apr 7, 2006, at 11:40 AM, Chris Lattner wrote: > On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: >> I just updated from CVS, and after doing a clean rebuild I get >> this error: > >

Here's why I was questioning the change to sample/lib/sample Makefile: make[4]: Entering directory `/proj/llvm/build/projects/sample/lib/sample' llvm[4]: Compiling sample.c for Debug build (PIC) llvm[4]: Linking Debug Shared Library sample.so llvm[4]: Linking Debug Object Library sample.o /proj/install/lib/libstdc++.a: member /proj/install/lib/libstdc++.a (allocator-inst.o) in archive is

When I tried this a while back, the .so file wasn't being built on Mac OS X. Now it looks like it is. I got dynamic loading to work following the instructions in http://llvm.cs.uiuc.edu/docs/ WritingAnLLVMPass.html. However, there was a typo in the instructions (it should say LOADABLE_MODULE = 1), and I fixed that and committed it. I also fixed the sample/lib/sample Makefile to

I haven't seen anyone claim x86 linux objdir == srcdir, so I'll test it out. Missed the 18th,but I'll try to have it done asap. On Apr 18, 2006, at 2:51 PM, Robert L. Bocchino Jr. wrote: > I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir. > > Rob > > On Apr 16, 2006, at 1:42 PM, Chris Lattner wrote: > >> On Sun, 16 Apr 2006, Tanya Lattner

The answer lies in the lib/System/ltdl.c which is the dynamic loader used by LLVM for cross platform dynamic loading. If there are paths or files that we're not looking for on OS/X then that needs to be fixed. Could you be a little more specific about what failures you are experiencing? Reid. On Fri, 2006-01-06 at 14:25 -0600, Robert L. Bocchino Jr. wrote: > Hi, > > > In the

I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir. Rob On Apr 16, 2006, at 1:42 PM, Chris Lattner wrote: > On Sun, 16 Apr 2006, Tanya Lattner wrote: >> For testing, we would like a mix of people to do x86 and ppc. >> Please send email to the list if you plan to test, what >> architecture, and if you will use the llvm-gcc binary or compile >> it

Hi, In the past, I haven't been able to get dynamically loaded passes to work under OS X. When I follow the instructions in the LLVM documentation, everything works fine for Linux, but OS X has a different way of handling dynamic loading, and the files that the dynamic loader is trained to look for don't exist. In the past, I've worked around this by just linking all my