similar to: [LLVMdev] LLVM for crosscompiling?

On Apr 5, 2008, at 3:31 PM, Sunjae Park wrote: > Hi, I am trying to use LLVM on x86 with some code intended for another > architecture (IBM Cell). The plan is: > > 1. foreach $c_files > llvm-gcc -emit-llvm -c -o $bc_file $c_file > 2. link $bc_files > 3. run my passes with 'opt' > 4. llc -march=c > 5. cell_cc > > The original code is for the Cell, and

On Sunday 06 April 2008 06:53:06 am Bill Wendling wrote: > (snip) > Hi Sunjae, > > You'll need to compile llvm-gcc as a cross-compiler to get it to > accept altivec intrinsics and PPC-specific flags. > > -bw Thanks, Bill. I was afraid of that. Any pointers on how to do this? I'm able to build llvm-gcc-4.2 x86 natively, but not the powerpc version. Using

Hi, I'm still working on this problem by first trying code without the Altivec intrinsics. I'm trying to use the cross compiler on the c code outputted by "llc -march c" and have run into this linker problem (spewed by the cross compiler): Command line : error: L0039: reference to undefined symbol .fopen64 in file /tmp/cc4tgLu5.o Command line : error: L0039: reference to

On Apr 6, 2008, at 11:24 AM, Sunjae Park wrote: > On Sunday 06 April 2008 06:53:06 am Bill Wendling wrote: >> (snip) >> Hi Sunjae, >> >> You'll need to compile llvm-gcc as a cross-compiler to get it to >> accept altivec intrinsics and PPC-specific flags. >> >> -bw > > Thanks, Bill. I was afraid of that. > > Any pointers on how to do

> If you want to use llvm-gcc as a cross compiler, you must configure it as > a cross compiler, and compile the output with the appropriate cross > toolchain. LLVM does not implicitly make your code portable, see: > http://llvm.org/docs/tutorial/LangImpl8.html#targetindep > > for example. > > -Chris Hm.. so the C backend works differently if I configure LLVM to be a cross

Hi all, I have a working package for linux, including fortran 95 code compiled with g95, that I need to port to OS X. The package works on Linux and seems to load on the Mac, but when I try to run a function that calls C or Fortran I'm told that the symbol is not loaded. I'm developing via a shell account on an OS X system, I don't have access to a desktop. The set up is: R

Hello. I know that it's usually possible to write cookies to a cookie file by removing the curl handle and doing a gc() call. I can do this with getURL(), but I just can't obtain the same results with postForm(). If I use: curlHandle <- getCurlHandle(cookiefile=FILE, cookiejar=FILE) and then do: getURL(http://example.com/script.cgi, curl=curlHandle) rm(curlHandle) gc() it's

Hi, Bernardo Fedora has a patch for LLVM 2.2 release with gcc 4.3 here: http://cvs.fedora.redhat.com/viewcvs/rpms/llvm/devel/llvm-2.2-gcc43.patch Just drop it in the llvm-2.2 directory and execute $ patch -p1 < llvm-2.2-gcc43.patch It should build cleanly afterwards. -- Sunjae Park MS. Georgia Tech College of Computing We choose to go to the moon and do the other things, not because they

~~~ Not to be applied, for discussion only ~~~ I think we need some kind of "checkpatch" script to catch all the annoying, nitpicky code style issues that submitters trip up on. I looked at a few scripts that exist, primarily the ones from Linux and qemu (massive and complicated), and libvirt (small and sane). There are a couple of problems: (1) Linux/qemu-style checkpatch only

Hi, I was trying to crosscompile dovecot, but I got some error: --with-notify=inotify don't work, as it try to run a test program to verify if inotify is supported in the building platform. Solved with --with-notify=dnotify. Ihmo, is more a hack than a solution. | checking whether posix_fallocate() works... configure: error: cannot run test program while cross compiling I can't

Hi folks, here're some quick+dirty fixes to allow sysroot'ed crosscompiling. probably not yet very clean, but seems to work. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: contact at metux.de

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

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

Hello, I am following this book Multitenancy with Rails. Has anyone here read this book or can shed light on the issue? When I run rspec i get following errors rspec spec/features/accounts/sign_up_spec.rb C:/Users/J/RubymineProjects/subscribem/spec/dummy/config/environments/test.rb:1:in `<top (required)>': undefined me thod `configure' for #<Dummy::Application:0x416fe08>

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:

Hi, I'm attempting to compile R 2.7.0 on my G5, which is running OSX 10.5.2. Yes, I know there is a precompiled binary, but my experience has shown that if I hand-compile ATLAS on my machine and then link R against it when compiling, R runs faster, hence me compiling it myself. Anyway, I have this set of errors: checking X11/Intrinsic.h usability... no checking X11/Intrinsic.h presence...

Hi Everyone, I'm having trouble figuring out a compile failure on ppc64le. The failure is at https://travis-ci.org/noloader/cryptopp-autotools/jobs/602187190 . The message is: /bin/bash ./libtool --tag=CXX --mode=compile clang++ -DHAVE_CONFIG_H -I. -DCRYPTOPP_DISABLE_POWER8 -pipe -mcpu=power7 -mvsx -maltivec -g -O2 -MT libppc_power7_la-ppc_power7.lo -MD -MP -MF

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lauro Ramos Venancio schreef: > 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

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