similar to: [LLVMdev] Basic question- cross compiling LLVM

On Mon, Jul 20, 2009 at 4:15 AM, Carter Cheng<carter_cheng at yahoo.com> wrote: > This is probably another very basic question- but is there a simple method for cross compiling LLVM for another platform? If you already have a cross-compiling environment set up, it shouldn't be too hard; for LLVM and llvm-gcc, you should be able to pass in --host=mytarget to configure, and if

Hello, I've just found that the current SVN trunk has some toolchain dependencies on ARM cross compiling. i.g. the __clear_cache in lib/System/Memory.cpp is not defined in my toolchain (codesourcery 2007q3, gcc version 4.2.1). What is the official(?) toolchain version used for ARM cross-compilation? Best, Hyok -------------- next part -------------- An HTML attachment was

Hello Evan and Robert I have been investigating the unexpected test failures from the ARM nightly builders in order to get a better picture why the ARM backend don't pass the whole testsuite: I have run the failing tests manually on my arm board and can now categorize most of the thirteen unexpected CodeGen failures in four categories: 1. llvm don't lower MVT::i64 properly on arm

LLVM ARM v6 backend is in fairly good shape. Even the JIT passes nearly the entire llvm test suite. There are some known missing bits: 1. Exception handling 2. Atomic Not sure: 3. Debugging support (should be trivial to hook up if it's not done) Also the thumb backend is not awesome. Its performance is not great. Evan On Apr 1, 2009, at 6:34 AM, Robert Schuster wrote: > Hi, > the

Hi, the ARM backend lacks some stuff like support for atomic intrinsics. I learned the hard way (crash). Lately I was told that the ARM backend of LLVM is generally in its early stages of development. I would like to know more about this. Which stuff is missing, known to be unstable and the like. Thanks in advance for taking the time. Regards Robert -------------- next part -------------- A

Hi Xerxes, > 4. softfloat related errors > http://labb.zafena.se/shark-testing/llvmARMCodeGenFailures200904/softenfloat_Do_not_know_how_to_soften_the_result_of_this_operator/ > example: > > root at overo:/home/xerxes/llvm-test/fail/CodeGen/softenfloat# llvm-as < 2007-11-19-VectorSplitting.ll | llc > SoftenFloatResult #0: 0x614e00: f32 = undef > llc:

I am curious- what is the current status of the MIPS support in LLVM? I have a mipsel device and was wondering if I could compile code for it with clang. Would I have to implement a backend setup myself? Is there also an option to compile w/ clang on an x86 for Mipsel? Thanks in advance.

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

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

I have been toying around with the LLVM tutorial code and I am trying to deduce what I can from it as a basis for a compiler frontend for a simple language of my own devising (once I understand what I am doing I will probably attempt mapping a more complex language target). I am having some difficulties however understanding how certain things work and I was hoping perhaps someone could help me

I apologize if this has been asked before but which classes utilize the information in these files? I am asking since I am trying to extend the MIPS backend to 64bit among other things. Thanks in advance, Carter.

Yes. But it is not really being used by most (any?) targets because post-RA scheduling is disabled by default. Also, the existing model is very limited in what types of micro-architectures can be described. I've been extending it to enable scheduling of multi-issue targets, targets with overlapping FU usage, and targets that use and define registers in multiple pipeline stages. See

On Mon, Jul 27, 2009 at 8:56 AM, Carter Cheng<carter_cheng at yahoo.com> wrote: > Is there also an option to compile w/ clang on an x86 for Mipsel? A normal build of clang includes limited cross-compile support by passing in the "-ccc-host-triple" option, although it's still a bit of a work-in-progress. Nobody has added support for any Mips targets, but it's really

Actually after some digging I managed to answer these questions for myself. I am guessing that this information is used by the Schedule* classes in CodeGen. --- On Mon, 8/17/09, Carter Cheng <carter_cheng at yahoo.com> wrote: > From: Carter Cheng <carter_cheng at yahoo.com> > Subject: [LLVMdev] ARMSchedule.td MipsSchedule.td etc. > To: llvmdev at cs.uiuc.edu > Date:

On Sun, Jun 28, 2009 at 1:05 AM, Carter Cheng<carter_cheng at yahoo.com> wrote: > 1) Using the Builder interface how does one create the equivalent of stack frames and access variables in the current stack frame or perhaps in the static enclosing scope (assuming functions can be nested)? To create stack variables, you can use the alloca instruction; see

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:

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. I haven't tried ARM, but this definitely works for crosscompiling from linux to mingw32. Please also note, that you'll need native (=arm) tools (binutils, libcheaders, etc) during gcc build

I've committed my scripts that simplify building Linux/x86 -> Linux/ARM crosstool. There are 2 parts to using this: * llvm/utils/crosstool/create-snapshots.sh creates tarballs for LLVM and LLVM-GCC from HEAD SVN or a specific revision of your choice * llvm/utils/crosstool/ARM/build-install-linux.sh builds and installs a Linux/x86 -> Linux/ARM crosstool using the snapshots generated

I am trying to create a boxed tagged datatype for a language where it is necessary to resolve the type at runtime. If I were writing an interpreter in C- it would most likely look something like this- struct { unsigned tag; union { long Int; double Float; .... } } Is there a standard way for constructing a type like this in LLVM? Thanks again.

Maybe is not what you want, but don't you crosscompile it for PPC, using toolchains in your desktop computer? It's suppose to be faster.