similar to: [LLVMdev] Linking libc statically to program and optimizations.

We are going to use LLVM in a compiler project for transport triggered processors. See Wikipedia for more on transport triggering: <http://en.wikipedia.org/wiki/Transport_Triggered_Architectures>. One thing we need is some sort of libc. We are targeting embedded systems, and I have been looking at things like newlib. Are there people out there doing something similar? Or any advice or

I have been browsing through the newlib documentation at <http://sources.redhat.com/newlib/> and pondering about how newlib relates to LLVM. Comments welcome, again. As I see it, there are basically two parts of libc that need to be considered. Much of libc is stuff like atoi(), isalpha(), etc. which are just convenience routines written in ANSI C. For these, it should be sufficient to

i am getting this compilation error: gcc -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../llvm-gcc-4.2-2.7.source/gcc -I../../llvm-gcc-4.2-2.7.source/gcc/.

You need to configure with --enable-llvm. (It would still be nice if V1DI_pointer_node was defined; I'll take a look at that.) On May 20, 2010, at 1:04 PM, Anatoly Yakovenko wrote: > i am getting this compilation error: > > > gcc -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall > -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic >

I am trying to build a cross compiler for arm on linux, here is how i have configured it cd llvm-gcc-4.2-2.7.source-objtree ../llvm-gcc-4.2-2.7.source/configure --enable-llvm=/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-2.7 --enable-multilib --enable-target-optspace --enable-interwork --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++

Hi, well, I downloaded the head revision of llvm and llvm-gcc. As you said it hangs at: Formal argument #0 has unhandled type f32 /home/julio/trunk/llvm-gcc/gcc/libgcc2.c:1765: internal compiler error: Abortado Please submit a full bug report, with preprocessed source if appropriate. Actually, I don't need fp, there is any way to disable? By the way, I'm working with a MIPS coprocessor

Hello, I'm trying to compile llvm-gcc to crosscompile mips. I have already modified a config.gcc to add mips as a target with llvm, but it gives me "Did not get a target machine!" (from llvm-backend.cpp). I thought that I had to modify TargetMachOWriterInfo.h with MIPS info, but now the problem is that I don't know where can I get the <mach/machine.h> (I don't have it

> ../llvm-gcc-4.2-2.7.source/configure > --enable-llvm=/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-2.7 > --enable-multilib --enable-target-optspace --enable-interwork > --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++ > --target=arm-elf This means that the compiler is built for ARMv4 which is not pretty good supported. Try to switch

And one last thing, the problem seems to be related to libcpp. Using only C frontend will work? 2008/7/7 Julio <julio.martin.hidalgo at gmail.com>: > Hi, well, I downloaded the head revision of llvm and llvm-gcc. As you said > it hangs at: > > Formal argument #0 has unhandled type f32 > /home/julio/trunk/llvm-gcc/gcc/libgcc2.c:1765: internal compiler error: > Abortado

Hi Koen, The process to build llvm-gcc as a crosscompiler is basically the same as build a normal gcc as crosscompiler. The differences: you need a LLVM installed (compiled for the host). You must configure llvm-gcc with --enable-llvm. Problems: - Today LLVM supports ARM/EABI, but llvm-gcc don't. You must apply the patch:

any ideas what library has these symbols lang_eh_catch_all get_pointer_alignment validate_arglist i get these linker errors when trying to link llvm-gcc: make[1]: Entering directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree' make[2]: Entering directory

Hi Julio, On Sun, Jul 6, 2008 at 1:58 PM, Julio <julio.martin.hidalgo at gmail.com> wrote: > Hello, I'm trying to compile llvm-gcc to crosscompile mips. I have already > modified a config.gcc to add mips as a target with llvm, but it gives me > "Did not get a target machine!" (from llvm-backend.cpp). > > I thought that I had to modify TargetMachOWriterInfo.h

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anton Korobeynikov schreef: > Hello, Koen. > >> So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 >> to ARM/EABI? > Well, just supply appropriate --host/--target options to configure. To llvm or llvm-gcc4? > I haven't tried ARM, but this definitely works for crosscompiling from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After hearing Chris' talk at bossaconference I wanted to see if I could use LLVM (and/or llvm-gcc) as a crosscompiler for ARM. The documentation beautifully outlines how to build it for your host and how to crosscompile it, but not how to build it as a cross-compiler. So my question is: How should I build llvm and llvm-gcc4 to have it

Hi Anatoly, > any ideas what library has these symbols > > lang_eh_catch_all > get_pointer_alignment > validate_arglist it sounds like you are trying to build a version of llvm-gcc without LLVM enabled. Did you specify --enable-llvm=path_to_llvm_build_directory when configuring llvm-gcc? These symbols are all defined in llvm-gcc itself, but only when ENABLE_LLVM is defined.

Hi LLVMDev, The GCC frontend for LLVM inserts a call to a __main() in the main() function. Whats the purpose of this? And which LLVM library do I need to link to satisfy the reference? Thanks, Rahul

As I have explained in another thread, I am in the process of porting portions of newlib to LLVM. The target system has no operating system and a custom processor which may be changed from compilation to compilation. We intend to use LLVM as the front end and generate target specific code from LLVM byte code. For various reasons (whole program optimization being one of them), it would seem to

On Sun, 2007-04-01 at 21:26 +0200, Koen Kooi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > After hearing Chris' talk at bossaconference I wanted to see if I could use LLVM (and/or > llvm-gcc) as a crosscompiler for ARM. The documentation beautifully outlines how to build > it for your host and how to crosscompile it, but not how to build it as a

Hi there, I'm trying to build llvm under cygwin running under windows xp, and have struck the following problem: -- llvm: tools-only built ok -- cfrontend: built ok -- llvm: full build failed at the following point: make[3]: Entering directory `/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend' Compiling crtend.c to bytecode Compiling listend.ll to bytecode Linking comp_main.bc

On Thu, 9 Nov 2006, Scott Michel wrote: > BTW: Would be nice if the frontend defined a manifest constant if it is > generating byte code vice generating native. But that's a refinement for > another day... Why? As an end user, I'd be very unhappy if I got different code from -emit-llvm + llc then from normal llvm-gcc. -Chris -- http://nondot.org/sabre/ http://llvm.org/