similar to: [LLVMdev] how clang reads the source data

hello,sir, i need your help,i have cloned the axtor code from the bitbucked (the url:https://bitbucket.org/gnarf/axtor.git),but i can not compile it.so can you help me to compile it?my E-mail:tshping at 163.com,so if you give me some advice,send me e-mail to there.thx so much. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I am new to LLVM and am trying to modify clang for some work. I tried to insert an instruction: prefetchnta $100 at the beginning of a function. I encountered a problem when I tried to debug it with gdb. There was an assertion failure and printed some information without stack trace. The process has been finished when it printed the information. I tried to set a breakpoint at the

Hi, here's the canonical helloworld.c #include<stdio.h> int main() { printf("Hello World"); return 0; } In accordance with the cross-compilation LLVM documentation [1], I am trying to target the ARM on the Zedboard [2]. It is an ARM Cortex-A9. The machine I am compiling on is an x86_64 Fedora Linux machine, using clang 3.3. I am failing to generate an executable,

Hi, my friends I know there is a difference between compiling a linux module and a simple helloworld programme. If I compile a helloworld.c file, the command is "clang -O3 -emit-llvm hello.c -c -o hello.bc" But what the command should be if I want to compile a linux module into a .bc file? (I know it may be an easy question to you guys, but I really don't know where to find the

On 11/27/2013 07:57 AM, Rob Stewart wrote: > On 26 November 2013 16:44, Renato Golin <renato.golin at linaro.org> wrote: >> On 26 November 2013 15:36, Rob Stewart <robstewart57 at gmail.com> wrote: >>> $ clang -v -target armv7a-linux-eabi -mcpu=cortex-a9 -mfloat-abi=soft >>> -mfpu=neon helloworld.c >> Hi Rod, > I'm honoured. (But Rob is also OK)

When trying to link more than one object files compiled with clang, I run into errors of the following type: $ clang -fblocks -g -I$HOME/opt/include -L$HOME/opt/lib/ -o helloworld helloworld.c hello.o world.o -lBlocksRuntime world.o: In function `gnu_dev_major': /usr/include/sys/sysmacros.h:43: multiple definition of `gnu_dev_major' hello.o:/usr/include/sys/sysmacros.h:43: first defined

On 26 November 2013 16:44, Renato Golin <renato.golin at linaro.org> wrote: > On 26 November 2013 15:36, Rob Stewart <robstewart57 at gmail.com> wrote: >> >> $ clang -v -target armv7a-linux-eabi -mcpu=cortex-a9 -mfloat-abi=soft >> -mfpu=neon helloworld.c > > Hi Rod, I'm honoured. (But Rob is also OK) :-) > You need cross-binutils installed on your

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

On 14/12/09 13:57, Abhishek Kulkarni wrote: > When trying to link more than one object files compiled with clang, I run into > errors of the following type: > > $ clang -fblocks -g -I$HOME/opt/include -L$HOME/opt/lib/ -o helloworld > helloworld.c hello.o world.o -lBlocksRuntime > world.o: In function `gnu_dev_major': > /usr/include/sys/sysmacros.h:43: multiple definition

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

2012/4/10 15102925731 <zhenkaixd at 126.com> > Hi, my friends > > > I know there is a difference between compiling a linux module and a simple > helloworld programme. > If I compile a helloworld.c file, the command is > *"clang -O3 -emit-llvm hello.c -c -o hello.bc"* > But what the command should be if I want to compile a linux module into a > .bc file?

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

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

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

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?

Hi everyone, I have a question that seems simple, but has been confounding me for several hours. I'd like to debug a binary produced with LLVM. For the life of me, I can't get any symbols into gdb and llvm-db won't even start the program nor load any useful information about it. Here's my current strategy (which isn't working): llvm-gcc -g -O0 -c -emit-llvm

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?

It's actually is .c file. I just want firstly to compile helloworldmodule.c into helloworldmodule.bc. Then I run a LLVM pass on it to do some optimization, and then I compile the modified .bc file into .ko file. So, could you tell me how to compile helloworldmodule.c into helloworldmodule.bc? I think it's not the same command "clang -O3 -emit-llvm hello.c -c -o hello.bc".

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