similar to: [LLVMdev] debugging LLVM generated executables???

Hi everyone again, I did discover the following works (see below). However, does anyone know of the "proper" way with LLVM? llvm-gcc -g -c -emit-llvm helloworld.c opt -load=mypass.dylib -mypass < helloworld.o > helloworld-mypass.o llc -fast -f -o helloworld.s helloworld-mypass.o as -o helloworld-prime.o gcc -o helloworld helloworld-prime.o gdb helloworld On May 5, 2008, at

I think you probably need to pass -O0 to llvm-ld. The link-time optimizations are probably killing your debug info. --Owen On May 5, 2008, at 8:21 PM, Mark Oskin wrote: > Hi everyone again, > > I did discover the following works (see below). However, does anyone > know of the "proper" way with LLVM? > > llvm-gcc -g -c -emit-llvm helloworld.c > opt

Just re-sending this. Anyone have any suggestions on how to proceed with debugging LLVM produced executables? The problem appears to be register-allocated variables. Global variables and syntax lines do get symbols using the llc / as method I described below. -Mark On May 6, 2008, at 7:36 AM, Mark Oskin wrote: > >> I think you probably need to pass -O0 to llvm-ld. The

> I think you probably need to pass -O0 to llvm-ld. The link-time > optimizations are probably killing your debug info. > No dice. Doing it this way makes gdb spew out this: warning: Could not find object file "/var/folders/cQ/cQ+L3+RP2RWOpE +8ZNQdPU+++TI/-Tmp-//ccVljWhn.o" - no debug information available for "defs.h" And then no debug symbols are available.

On Wed, 7 May 2008, Mark Oskin wrote: > Just re-sending this. Anyone have any suggestions on how to proceed > with debugging LLVM produced executables? The problem appears to be > register-allocated variables. Global variables and syntax lines do > get symbols using the llc / as method I described below. -Mark Have you considered adding your pass to llvm-backend.cpp in llvmgcc?

I could do that, but before I venture there, if I did that, could I have llvm-gcc produce native object files (not LLVM bytecode) that way (using my pass)? thanks, -Mark On May 7, 2008, at 11:40 AM, Chris Lattner wrote: > On Wed, 7 May 2008, Mark Oskin wrote: >> Just re-sending this. Anyone have any suggestions on how to proceed >> with debugging LLVM produced executables?

I have seen INITIALIZE_PASS(LiveVariables, "livevars", "Live Variable Analysis", false, false); in the llvm/lib/codegen/LiveVariables.cpp, where LiveVariables is a subclass of MachineFunctionPass, and #define INITIALIZE_PASS(passName, arg, name, cfg, analysis) \ static RegisterPass<passName> passName ## _info(arg, name, cfg, analysis) in PassSupport.h Is this code used

Hi, I'm trying to implement a module pass as a share object to process an entire program as a unit. The target program is built from multiple object files, hence multiple bitcode files. However, it seems that opt does not take the whole program, but just one bitcode file, "test.bc" in the example run shown below. $ opt -load mypass.dylib -mymodulepass < test.bc > /dev/null

Hi, I am trying to use some LLVM API in my C++ code, and I end up getting linker errors. I am working on Apple MacOSX Lion. Using g++ for the compile. It is the CreateGlobalStringPtr which is throwing the error. This is LLVM 3.0. Here's the codeI am trying to use some LLVM API in my C++ code, and I end up getting linker errors. I am working on Apple MacOSX Lion. Using g++ for the compile. It

Probably your g++ compiles x86_64 binary by default, but i686 dylib is supplied? Try: g++ -m32 e.cpp /Developer/Platforms/iPhoneOS.platform/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin10/4.2.1/libllvmgcc.dylib - D. 2012/1/22 Arpan Sen <arpansen at gmail.com>: > Hi, > > I am trying to use some LLVM API in my C++ code, and I end up getting linker > errors. I am

Hi, I try to make my first package? The HelloWorld.R file is: #### HelloWorld.R #### #' showHello est une fonction R permettant d'afficher le message #' "Hello World!" sur la console. #' @title la fonction showHello() showHello <-function(){ cat("Hello World!\n") } I use the following procedure to get the tar: # set the working directory where the file is

Thanks John. Your approach worked fine for my small toy program. Now, I would like to run my module pass on a huge project (still a single executable) consisting of a few thousand bit code files scattered in many different directories. And some of them are static libraries. Do you still think it's a good idea to manually gather and link them with llvm-ld? I've seen other module pass

Hello LLVM, I am following the document "Writing an LLVM Pass". When I ran "opt -load ../../../Debug/lib/MyPass.so -mypass < hello.bc > /dev/null" I got the next error: ***@ubuntu:~/test$ opt -load ../../llvm/Debug/lib/MyPass.so -mypass < hello.bc > /dev/null opt: Pass.cpp:159: void<unnamed>::PassRegistrar::RegisterPass(const llvm::PassInfo&): Assertion

Juan Carlos Martinez Santos wrote: > Hello LLVM, > > I am following the document "Writing an LLVM Pass". When I ran "opt > -load ../../../Debug/lib/MyPass.so -mypass < hello.bc > /dev/null" I > got the next error: > > ***@ubuntu:~/test$ opt -load ../../llvm/Debug/lib/MyPass.so -mypass < > hello.bc > /dev/null > opt: Pass.cpp:159:

Hi everyone, I have been attempting to build a very simple R package interfacing with some very simple C++ code. Everything I try though results in the function working but on return it produces a memory error. Here is the output: ***********OUTPUT*************************** > library(MyPackage) > hello(); *** caught segfault *** address 0x3, cause 'memory not mapped'

Hi Rui, I still fail to enable the lld in my Uefi firmware build to replace ld, and I found it is related to the wrong symbol values in the .data section, which are pointed by R_X86_64_64 relocation entries. I need your advices. My firmware uses a linker script https://github.com/tianocore/edk2/blob/master/BaseTools/Scripts/GccBase.lds to do the linking. We use position independent code with

Hi again, I come back to this issue with an example. It's a pass which does nothing but throw the 'Unable to schedule' error. namespace { struct MyPass : public FunctionPass { static char ID; // Pass identification, replacement for typeid MyPass() : FunctionPass(ID) { initializeMyPassPass(*PassRegistry::getPassRegistry()); } virtual void

How do you compile the code? Within the Polly subdirectory using CMake? How do you run your pass. Using "opt -mypass inputfile.ll"? Michael 2018-01-28 9:30 GMT-06:00 hameeza ahmed via llvm-dev <llvm-dev at lists.llvm.org>: > Hello, > > I need to analyze dependencies in my llvm ir by using polly. i created a new > pass called mypass there i added polly dependency

On 7/12/11 4:11 PM, Jinwook Shin (HOTWING) wrote: > > Hi, > > I'm trying to implement a module pass as a share object to process an > entire program as a unit. The target program is built from multiple > object files, hence multiple bitcode files. However, it seems that opt > does not take the whole program, but just one bitcode file, "test.bc" > in the

Hello, I am having difficulty getting any sort of LXC container running. I am trying to use the following tutorial to run the hello world example: https://www.berrange.com/posts/2011/09/27/getting-started-with-lxc-using-libvirt/ Here are the results of my running the tutorial: [root@terraria ~]# virsh list Id Name State