similar to: [LLVMdev] Error: Program contains no debugging information!

Dear Prof. Adve, Now I can use llvmgcc to compile a .c file into .bc file. But I still have trouble simply run the .bc code. Below is the sequence I got when I tried. I really don't know what's going on here. Please let me know how can I fix it. Thanks, xiaodong xli3|csil-suna48|~/cs426|[13]% llvmgcc scalarize.c -o scalarize xli3|csil-suna48|~/cs426|[14]% scalarize Cannot load value of

Thanks, Chris, Below is the output of 'llvmgcc he.c -v' xli3|csil-suna27|~/cs426|[35]% llvmgcc he.c -v Reading specs from /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-lib/llvm/3.1/specs Configured with: /home/vadve/lattner/cvs/gcc/configure --srcdir=/home/vadve/lattner/cvs/gcc --prefix=/home/vadve/lattner/cvs/gcc_install_sparc --target=llvm --enable-languages=c

On Wed, 28 Jul 2004, Reid Spencer wrote: > 2. MODE OF OPERATION > ==================== > The driver will simply read its command line arguments, read its > configuration data, and invoke the compilation, linking, and > optimization tools necessary to complete the user's request. Its basic I'm not sure that I agree with this. Compilers need to be extremely predictable and

Hi all, I'm using trunk version of LLVM/CLANG. When I compile attached files on my 64-bit Ubuntu 10.04 LTS system as follows: clang -O2 -g check.c main.c -o check64 When I do gdb check64 and set a breakpoint to the check routine and executes to the breakpoint, I've got: Breakpoint 1, check (result=0x601110, expect=0x601020, n=53) at check.c:7 7 { As you can see I can inspect

Hi Tobias, > I committed an extended version of that patch to llvm core and the test suite. > Can you have a look, if it works for you. if I configure like this then the configure script thinks llvm-gcc is not dragonegg: configure --with-llvmgcc="gcc-4.5 -fplugin=path/dragonegg.so" --with-llvmgxx="g++-4.5 -fplugin=path/dragonegg.so" There are several reasons for

On Wed, 2004-07-28 at 11:26, Chris Lattner wrote: > On Wed, 28 Jul 2004, Reid Spencer wrote: > > 2. MODE OF OPERATION > > ==================== > > The driver will simply read its command line arguments, read its > > configuration data, and invoke the compilation, linking, and > > optimization tools necessary to complete the user's request. Its basic > >

Hi James, clang is able to generate correct debug informations for 64-bit target at -O2. My feeling, given some other experiments I've done, is that debug information generated for x86 32-bit might be broken for parameters as long as they are not 'homed' in the code (local copy to an automatic variable). It seems that when llvm.declare is turned into a llvm.value for parameter there

--- Mike Mestnik <cheako911@yahoo.com> wrote: > Date: Fri, 25 Jun 2004 09:51:21 -0700 (PDT) > From: Mike Mestnik <cheako911@yahoo.com> > Subject: Re: IPP2P: Simular project l7-filter. > To: Eicke Friedrich <tady@gmx.net> > > --- Eicke Friedrich <tady@gmx.net> wrote: > > Mike Mestnik wrote: > > > http://sourceforge.net/projects/l7-filter/

Good day sir and Thank you Luke for replying. Whatever U told about the things like accounts on linux and windows machine and adding a user to smbpasswd with -a option but still it is not woriking. Please help me . Thanks in advance. --- Luke Roberts <Luke.Roberts@isispc.com.au> wrote: > Hi Prakesh, > > Do you have linux user accounts to match your > windows

Simple Case: 1.int main() 2.{ 3. int i = 0; 4. return 0; 5.} compile command: clang -g a.c In LLVM IR, we have one attribute named "scopeLine" to indicate the left parentheses. But we don't have one attribute to indicate the right parentheses (line 5 in this example). So if we use gdb to debug it: (gdb) b main Breakpoint 1 at 0x100005c8: file a.c, line 3. (gdb) r Breakpoint

I bought a Cisco 7940, I need to configure it for Asterisk. I checked the wiki pages. Followed the link to Cisco web page. Tried to download the image for SIP. It wo'nt allow me even though I registered for the CCO Valet. Is the image available anywhere else? I saw some of the messages in the mailing list that it supposed to be fairly simple. I would highly appreciate if somone could post

I don't understand it. It was working fine a month ago. Now it just does not work. Is any one having problems with Up2date? Thanks __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail

Finally lli and llvmgcc can work under my directory. I wrote the following simple program and compiled it using gcc and then run it without any problem. But when I tried to compile it using llvmgcc and lli, llvmgcc gave me the following error message which I cannot understand: xli3|csil-suna37|~/cs426|[181]% llvmgcc test.c -o test test.c: In function `init': test.c:10: warning: cast to

LGTM. I think you can sent patch and let the ball rolling! I would like to review it. ;) 2018-03-28 10:41 GMT+08:00 Hsiangkai Wang via llvm-dev <llvm-dev at lists.llvm.org>: > Hello all, > > I would like to enhance LLVM debug info that supports setting > breakpoint on labels in function. > > Generally, if users use GDB as their debugger, they could set > breakpoints on

Sounds good to me. You can also see llvm.codeview.annotation which does a similar thing, but it is modeled as having internal, invisible side effects. These should stay separate, but it may provide a guide for implementation. On Tue, Mar 27, 2018 at 7:41 PM Hsiangkai Wang via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hello all, > > I would like to enhance LLVM debug info

Hi, I'm trying to compile two files together with debug information but seems that LLVM is getting the DW_AT_stmt_list wrong when ld is linking the final executable. Originally, I tried on ARM with Clang (+llc+gas+ln) and, the object files, the DW_AT_stmt_list were null, as expected. When linking, they should point to the offset in the line table, but all of them are still null, so pointing

> > On Mar 27, 2018, at 7:41 PM, Hsiangkai Wang via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello all, > > I would like to enhance LLVM debug info that supports setting > breakpoint on labels in function. > > Generally, if users use GDB as their debugger, they could set > breakpoints on labels in function. Following is an example. > > // C

On Wed, Mar 7, 2012 at 6:50 AM, Seb <babslachem at gmail.com> wrote: > Hi James, > > I fully agree with you and understand your statement about -O2. > > Now some questions for you: > Did you try to reproduce experiments described in my previous e-mail ? > Did you look at debug informations generated for 'n' parameter on x86 32-bit > & x86 64-bit ? >

Dear llvm, I just tried to compile a simple file hello.c. But each time I used llvmgcc hello.c, it gave me the following error: xli3|csil-suna33|~/cs426|[13]% llvmgcc hello.c as: error opening '/var/tmp//ccapglpE.o': file exists! Use -f command line argument to force output I really got confused. Could you please let me know what's wrong? thanks, Jerry

Valery A.Khamenya wrote: >>For example: >>$ llvmgcc ackerman.c -o ackerman -Wl,-native-cbe > > > BTW, Chris, what should be then an analogy > of "gcc -O3 -S foo.c" in LLVM framework? > > The invocation of > > $ llvmgcc -S ackerman.c -o ackerman -Wl,-native-cbe > > does not produce native assebler output as one might expect.