similar to: [LLVMdev] Compilation error while cross compiling LLVM for ARM

Prasanth J skrev: > Hi, > > i am a newbie to llvm architecture. i have been trying to port llvm on > ARM target. i am using the following configuration for cross compiling > llvm. > > ../llvm/configure --host=arm-linux --target=arm-linux > --build=i686-linux --prefix=/opt/llvm-arm/ --enable-optimized > --disable-debug \ > --disable-expensive-checks --disable-doxygen

Hi all, with reference to the reply below, I downloaded toolchain from codesourcery (arm-2009q1-203-arm-none-linux-gnueabi) with gcc 4.3.3... when i compile llvm+clang with this toolchain i am getting the following error make[4]: Entering directory `/home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm-obj/tools/clang/tools/c-index-test' llvm[4]: Linking Release executable c-index-test (without

Prasanth J wrote: > > Hi all, > with reference to the reply below, I downloaded toolchain from > codesourcery (arm-2009q1-203-arm-none-linux-gnueabi) with gcc 4.3.3... > when i compile llvm+clang with this toolchain i am getting the > following error > > make[4]: Entering directory >

Prasanth J wrote: > Hi, > > As you said i downloaded arm toolchain from codesourcery(2009q3 with > gcc 4.4.1 version).. if i use this toolchain i am getting the > following error.. > > make[2]: Entering directory > `/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib/Analysis' > llvm[2]: Compiling LoopPass.cpp for Release build > if arm-none-linux-gnueabi-g++

Hi, As you said i downloaded arm toolchain from codesourcery(2009q3 with gcc 4.4.1 version).. if i use this toolchain i am getting the following error.. make[2]: Entering directory `/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib/Analysis' llvm[2]: Compiling LoopPass.cpp for Release build if arm-none-linux-gnueabi-g++ -I/home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm/include

Hi, I can able to compile LLVM using armgcc_4.3.3 (codesourcery2009q1..).. but when i tried to run it on target it shows GCC 4.3.0 version not found. So i copied the runtime libraries (libc.so and libgcc_s.so) from the toolchain to the target and exported its path in LD_LIBRARY_PATH. But when i tried to run any llvm tools on target its crashing with Segmentation fault. What could be the problem

Prasanth J wrote: > Hi, > > I can able to compile LLVM using armgcc_4.3.3 (codesourcery2009q1..).. > but when i tried to run it on target it shows GCC 4.3.0 version not > found. So i copied the runtime libraries (libc.so and libgcc_s.so) > from the toolchain to the target and exported its path in > LD_LIBRARY_PATH. But when i tried to run any llvm tools on target its >

Hi all, I am in the process of developing a installer utility for ARM target which can compile any source files to ARM native executable. This installer utility should be present on target itself (whether this is feasible or not?). For achieving this i compiled llvm with clang for target. I copied the binaries to target and when it tried to compile a sample c code i am getting the following

Dear Duncan Murdoch: Thanks for your tips. By the way, I think I didn't mentioned my question very clear. What I mean to say is that, in Excel one could decide upon the axis interval unit. Please see the attached file. Likewise, is it possible in R...? Regards, Prasanth. -----Original Message----- From: Duncan Murdoch [mailto:murdoch at stats.uwo.ca] Sent: Tuesday, March 31, 2009 6:25 PM

Sorry i really forgot to mention one thing. I downloaded the X86 binaries of llvm+clang and llvm-gcc from llvm download site. i hope that is not a debug build. Prasanth J On Sun, Nov 15, 2009 at 1:22 PM, Prasanth J <j.prasanth.j at gmail.com> wrote: > Hi all, > > LLVM is built without debug enabled. Also i am not forcing lli to use > interpreter mode. so i dont think the

Dear R Users: Greetings! Is there any way to specify the axis interval unit for barplots in R.? Any help is deeply appreciated. Thanks in advance! Prasanth VP, Global Manager - Biometrics, Delta Technology & Management Services Pvt Ltd, Plot No: 13/2, Sector - I, Third Floor, HUDA Techno Enclave, Madhapur, Hyderabad - 500 033. Office : +91-40-3028 0659 Mobile : +91-9848

llvm/lib/System/Atomic.cpp contains the call to __sync_val_compare_and_swap that lowers to the missing __sync_val_compare_and_swap_4 GCC intrinsic. The same file contains several other __sync_* calls and all these has to be implemented if we want to be able to compile llvm on linux/ARM with GCC versions below < 4.4 xerxes at labbserver:~/llvm$ grep _sync lib/*/* lib/System/Atomic.cpp:

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

Hi all, I have attached the complete test suite. it has different directories for gcc, llvm-gcc , clang and lli-clang. Source code , makefile and run script (contains number of times the program should execute) for each case are available inside each directory. * FOLLOWING ARE THE STATISTICS WHILE USING LLI FOR SINGLE ITERATION*

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

Why is his configure not catching this? It tests for the linkability of these functions on the target arch, and should be detecting their absence if that is actually the case. --Owen On Jul 1, 2009, at 12:50 AM, Xerxes Rånby wrote: > llvm/lib/System/Atomic.cpp contains the call to > __sync_val_compare_and_swap that lowers to the missing > __sync_val_compare_and_swap_4 GCC

Hi all, LLVM is built without debug enabled. Also i am not forcing lli to use interpreter mode. so i dont think the reason is not because of debug build or interpreter mode. *step 1: * compiled the 3 files (generic_replica.c ,xacc.c and dacc.c) with clang-cc to llvm bytecode files using -emit-llvm-bc and (-O0/-O3) options *step 2:* bytecode obtained from step 1 (generic_replica.bc, xacc.bc and

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

Dear R Users, Greetings! I am confused with an error message related to "plotrix" library in the newer versions of R. I used to run an R script without fail in the earlier versions (R 2.8.1) of R; but the same script is now throwing up an error message in the newer versions (Now I have R 2.13.0 & R 2.14.0). Herewith I am furnishing the same code for your perusal. It would

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: