similar to: [LLVMdev] Debugging using gdb

Pranav Garg wrote: > Hi, > > I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. > However I am not able to establish a breakpoint in any function of my > pass. I have compiled my > pass with a debug build and I have also compiled the input file (using > llvm-gcc) with the -g flag. Given below is the exact output. > > > (gdb) break

Hi John, Yes, it was the problem of the namespace. Sorry for bugging for such a silly mistake. Thanks Pranav On Mon, Apr 19, 2010 at 9:33 AM, John Criswell <criswell at uiuc.edu> wrote: > Pranav Garg wrote: > >> Hi, >> >> I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. >> However I am not able to establish a breakpoint in any function 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

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

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

LiveVariables gives you something like liveness analysis: where each variable is alive, that is, across each basic blocks, where it is defined, and where it is killed. LiveIntervals gives you a linear representation of the variables as a set of intervals. Yes, it handle holes in the live ranges. There is a very nice description of these analysis and related data structures here:

Dear LLVM: I wrote a small testcase and I can compiler and run it with gcc, But with llvm, I got weird error like the following. I really don't know what's going on. Could you explain? Thanks a lot -Jerry Error Message: xli3|csil-suna38|~/mp2|[25]% llvmgcc testcase3.c testcase3.c: In function `init': testcase3.c:5: warning: cast to pointer from integer of different size

On 4/3/07, David Greene <greened at obbligato.org> wrote: > > Toward a better register allocator, I'm attempting to understand > the dataflow information available to the allocator. > > What's the difference between LiveInterval information and LiveVariable > information? If a LiveInterval is based on a linear ordering of > the machine instructions, isn't it

When I tried to run the previous .bc code with lli, I got the following errors: xli3|csil-suna33|~/cs426|[48]% lli he2.bc Unresolvable reference found: <long>:1! Unresolvable reference found: <long>:1! Unresolvable reference found: <long>:2! Error parsing 'he2.bc': No module loaded: Error resolving method values! So right now, I cannot do anything. Could you please let

When I check out llvm this morning. I got this error, so I couldn't check out. Looks like the disk is full.. Please let me know how to fix this problem. Thanks, xiaodong xli3|csil-suna33|/usr/dcs/projects/cs426/xli3/llvm|[10]% cvs update cvs update: Updating . ? gnumake.out cvs update: Updating Support cvs update: Updating include cvs update: Updating include/Support cvs update: cannot close

The problem with llvmgcc invoking as instead of llvm-as has been fixed. 3 llvm-specific executables needed to be copied into a default location where gcc can find them if it does not find them as configured (gcc was configured for the paths on our research machines and copied over). Let us know if you have additional problems. --Vikram > -----Original Message----- > From: llvmdev-admin

Fernando Magno Quintao Pereira wrote: > LiveVariables gives you something like liveness analysis: where each > variable is alive, that is, across each basic blocks, where it is defined, > and where it is killed. If I read this correctly, it means that at each instruction there's a list of live variables? I'm trying to figure out how to get at this information to build the

yes I think that is correct. I wrote a simple program to print if sizeof(uintptr_t) != sizeof(unsigned char *) and when I compile with gcc -m64 and execute it on a 64-bit host (that is different from the 32-bit laptop on which I originally compiled the program), it says the sizes are not equal. Thanks Pranav On Thu, Aug 1, 2013 at 9:29 AM, Alexey Samsonov <samsonov at google.com> wrote:

Dear Alexey, Yes I am sure that the llvm, clang and compiler-rt are synced to the same version. I downloaded them all from git http://llvm.org/docs/GettingStarted.html#git-mirror I think I need compiler-rt for my project but I'll verify it again to see if I can proceed without it. You are correct that compiler-rt is compiled with the just built clang. The complete command that gives an error

Hi, In the quest for better test cases for my MP, I thought of trying the Stepanov Abstraction Penalty benchmark. But apparently llvm-g++ is not ready for such terrible things. Let me know if you want me to send the source code (it is widely available). gaeke|csil-suna37|~/cs/426/MP1/step|[1177]% /usr/dcs/projects/cs426/Software/gcc_install/bin/g++ stepanov.cpp -o stepanov In file included from

Hi, I see that ENABLE_WERROR is being set to off (the default value) in the config.log in the llvm build. However on grepping for WERROR in the compiler-rt folder I get the following output: pranav at pranav:~/smack-project/llvm-3.4/src/projects/compiler-rt$ grep -Rin WERROR * lib/asan/tests/CMakeLists.txt:38: -Werror lib/asan/asan_malloc_mac.cc:253:// This function is currently unused, and we

On Thu, Aug 1, 2013 at 5:32 PM, Pranav Garg <pranav.garg2107 at gmail.com>wrote: > Dear Alexey, > > Yes I am sure that the llvm, clang and compiler-rt are synced to the same > version. I downloaded them all from git > http://llvm.org/docs/GettingStarted.html#git-mirror > I think I need compiler-rt for my project but I'll verify it again to see > if I can proceed

Hi, I am trying to build llvm along with clang and compiler-rt. When I run make, I am getting the following compilation error (I tried compiling llvm-3.2, which is what I need for my project, but also tried llvm-3.3 and the current llvm source from the git repository). ... COMPILE: clang_linux/full-x86_64/x86_64:

Hi Pranav, On Thu, Aug 1, 2013 at 1:54 AM, Pranav Garg <pranav.garg2107 at gmail.com>wrote: > Hi, > > I see that ENABLE_WERROR is being set to off (the default value) in the > config.log in the llvm build. However on grepping for WERROR in the > compiler-rt folder I get the following output: > > pranav at pranav:~/smack-project/llvm-3.4/src/projects/compiler-rt$ grep

On 4/30/2014 5:24 PM, Craig Topper wrote: > Pranav, can you remove it? > Yes, I'll remove it. Pranav -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation