similar to: [LLVMdev] Linux Kernel Compile for Sparc v8 Arch

On Sep 28, 2008, at 9:46 PM, Keun Soo Yim wrote: > > Does anyone succeed at compiling Linux kernel for Sparc v8 > architecture? > I am currently trying to expand the regime of LLVM to Sparc kernel > codes. > The following is the initial error messages. Any comment is welcomed. > > #1. Inline Assembly The Sparc backend has no active maintainer [1]. This

On 2008-09-29 07:46, Keun Soo Yim wrote: > Does anyone succeed at compiling Linux kernel for Sparc v8 architecture? > I am currently trying to expand the regime of LLVM to Sparc kernel codes. > The following is the initial error messages. Any comment is welcomed. > > #1. Inline Assembly > > > > Code: > > register struct thread_info

Does anyone succeed at compiling Linux kernel for Sparc v8 architecture? I am currently trying to expand the regime of LLVM to Sparc kernel codes. The following is the initial error messages. Any comment is welcomed. #1. Inline Assembly Code: register struct thread_info *current_thread_info_reg asm("g6"); Error Message: include/asm/thread_info.h:77: error:

Hi, I have couple of questions that those who design unconventional passes would be interested in. 1. How to move a virtual register data to another new virtual register? It seems like that there is no LLVM instruction similar to mov machine instruction. Arithmetic or logical operators could be used for integer variables but what about pointer variables? 2. What is

Hi, The source attached at the bottom is a testcase which causes a back-end error in LLVM 2.4. These types of assembly routines are mainly used in OS kernels. I checked that GCC 4.3 works for this routine. The error messsage is ... Couldn't allocate output reg for constraint 'A'! I just need help or comments so that I could analyze and fix this bug. My

Thank your for reply. The reason why these information are needed is that I am trying to extract the program signature (e.g., control flow) out side of the binary. Conventional compiler technique adds extra checking code into the target source or target IR in an invasive manner. Since code generator combines the added code with the original one, they don't need to correlate these two

Mark Kromis wrote: > On Dec 27, 2008, at 7:41 PM, Misha Brukman wrote: >> 2008/12/27 Mark Kromis <greybird at mac.com> >> Just a curiosity question, why push for gtest vs Boost Test or a >> different test suite? >> I normally use Boost, and their test suite, so I'm more familiar with >> that. So I was wondering is one better then the other, or is it

Can you bootstrap llvm-gcc (configure with --enable-bootstrap)? Ciao, Duncan.

Keun Soo Yim wrote: > > Hi, > > How to correlate the LLVM IR-leve instructions and memory values > with the machine instructions and memory locations? Can you tell us what goal you are trying to accomplish that requires you to do this? There might be better ways of doing what you want. The answer to your question probably depends on whether you're trying to write a

>> Dear All, I have been trying for days but still cannot break this barrier. May I get your help? I have compiled llvm-2.1 successfully and make install. When I proceed with llvm-gcc-4.2-2.1, however, I keep getting linking error as attached. Some functions with totally different content conflict with each other in linking process. That is a Linux box (Debian, with 2.6.23-1

Keun Soo Yim wrote: > > Please run… > > $ llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc > > $ llvm-dis < hello.bc > hello.ll > > The first command is to generate a byte code > > and second is to translate the bytecode to a readable form. > llvm-gcc can emit the textual form directly too: llvm-gcc -O2 -emit-llvm hello.c -S -o hello.ll llvm-gcc -O2 -emit-llvm

Hi, How to correlate the LLVM IR-leve instructions and memory values with the machine instructions and memory locations? For example, if CMP instruction in machine ISA is selected for the ICMP instruction in LLVA, with the Instruction datastructure for ICMP, is it possible to get the memory address of CMP instruction? Assume that the code segment base address is given. Similarly, by

Hello, I’m trying the following thing: • build and install llvm with mgcc (system compiler) • build and install llvm-gcc with mgcc • build llvm with llvm-gcc • deinstall llvm(old), install llvm(new) • build llvm-gcc with llvm-gcc(old) • deinstall llvm-gcc(old), install llvm-gcc(new) However, I have the problem that the llvm-gcc(new) does not work: after it is compiled, it tries to build libgcc2

Hi, This is a simple question about building ARM cross-compiler. What is the building procedure using LLVM 2.4 and GCC front-end 4.2? I used these commands for LLVM, and it is okay. $ ../configure --prefix=/usr/local -target=arm $ make ENABLE_OPTIMIZED=0 $ make ENABLE_OPTIMIZED=0 install Then these commands were used for GCC front-end but this got couple of errors. $ ../configure

On Feb 12, 2009, at 11:25 PM, Tielei Wang wrote: > Hi, every body, > > I get stuck when trying to build llvm-gcc4.2-2.4 on x86_64 Linux with > GCC-4.3.3. I meet this error: Make sure to follow the README.LLVM file in the llvm-gcc distro. llvm- gcc doesn't support gcj yet at all. -Chris

Hi, I am having some difficulties building llvm on Itanium. My procedure for building LLVM is: cd /liberty/llvm.ia64/llvm-2.1 ./configure make ENABLE_OPTIZED=1 cd /liberty/llvm.ia64/obj /liberty/llvm.ia64/llvm-gcc4.2-2.1.source/configure --prefix=/liberty/llvm.ia64/install --enable-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++ --disable-shared The build of llvm seems to

Hi, every body, I get stuck when trying to build llvm-gcc4.2-2.4 on x86_64 Linux with GCC-4.3.3. I meet this error: make[3]: Entering directory `/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/gcc' /home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/xgcc -B/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings

I first install the gcc-4.2.4 . then I set CC and CXX export CC= "path of my gcc-4.2.4" export CXX="path of my g++-4.2.4" after that , I config and make . error occur like this : /home/ws/software/gcc-4-2/bin/gcc -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros

On Mar 11, 2009, at 9:44 PM, Misha Brukman wrote: > The problem I've had is building an LLVM cross-compiler from Linux/ > x86 to Linux/ARM (as has another llvm-dev poster). Someone > mentioned to me off-list that he managed to get it to build, but I > haven't been able to reproduce the build using his instructions > (I'll post my results in another thread).

Hi, I've figured out a little more. #if defined DBX_DEBUGGING_INFO || XCOFF_DEBUGGING_INFO guards the declaration of type_queue, however, neither is defined on Intanium. In gt-dbxout.h type_queue's uses are unguarded and thus are undefined on Itanium. When I compared llvm-gcc's gt-dbxout.h with FSF gcc's, I found that type_queue was never used in FSF gcc's version. Does