similar to: [LLVMdev] About LLVM 3.1 ARM testing

On Sat, Apr 14, 2012 at 4:13 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi all, > > Since the 3.1 testing day is coming and be a ARM tester, I would like to > make > sure everything is O.K. so that we don't waste the precious time. As > discussed > on the ML before, I plan to cross compile LLVM/Clang first, then run > regression > test and test suite on

> Ubuntu on ARM is softfp, right? How about testing hardfp with a > distribution like ArchLinuxArm? Yes, Ubuntu on ARM is softfp. But I already told Bill the platform I prepare to test and the testing day begins *tomorrow*, I prefer what it likes now. BTW, what if I use a cross compiler with hardfp enabled to compile LLVM first, then run it on Ubuntu/ARM? Does it achieve your goal, too?

On Sun, Apr 15, 2012 at 2:02 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > > Ubuntu on ARM is softfp, right? How about testing hardfp with a > > distribution like ArchLinuxArm? > > Yes, Ubuntu on ARM is softfp. But I already told Bill the platform I > prepare > to test and the testing day begins *tomorrow*, I prefer what it likes now. > BTW, > what if I use

Hi list, I want to use LLVM to compile the C code to arm. Host: Mac OS X 10.10 Target: Pandaboard, armv7l, ubuntu I found some useful information but not worked yet. I tried like this: $ clang -fomit-frame-pointer -ggdb -emit-llvm --target=armv7l-unknown-linux-eabi -mcpu=cortex-a9 —mfpu=neon -mfloat-abi=softfp --sysroot=/... test.c -c -o test.bc --> clang-3.5: error: no such file

Hi Renato, > 1. Some ARM triples "arm*-none-eabi" don't get properly recognized, > so Clang doesn't generate correct AAPCS (soft and hard) calls and > don't pass the correct triple to LLC. in order to have "eabi" be properly recognized by LLVM, it is enough to add "eabi" as a valid environment value. Then Triple::Normalize will automatically

Hi Óscar, On Tue, Sep 11, 2012 at 04:45:23AM +0200, Óscar Fuentes wrote: > "陳韋任 (Wei-Ren Chen)" <chenwj at iis.sinica.edu.tw> writes: > > > I have been stuck on compiling LLVM/Clang (r163485) on pandaboard which has > > following configuration, > > > > - Ubuntu 11.04 + 1G Mem + 1G Swap + 32G SD card > > - GCC 4.5.2 > > - GNU gold

Hi all, There's been some controversies in the TargetTriple changes and I want to explain it better in the list (to a wider audience) and also propose my plans on how to support the ARM platform better, especially cross-compilation in Clang. All this discussion came as a spin-off of bug 8911 (http://llvm.org/bugs/show_bug.cgi?id=8957)... Today we have three major problems in cross-compiling

Targetting the raspberry pi, what triple/flags should I set? I tried triple: armv4t-unknown-linux-gnueabi and ld fails with: a.out uses VFP register arguments if i set hardfloat (using optdata.FloatABIType = FloatABI::Hard), ld fails with an assertion: 2.22 assertion fail ../../bfd/elf32-arm.c:11477 what am I missing?

Hello, I played with Clang + LLVM 3.1 release on ARM Linux and suspected it is incompatible with GCC. My program works fine while compiled using GCC but will crash with Clang. Specifically, the alignment strategy of Clang confused me. I wrote a small program to print the structure layout of the following and compiled it with both Clang and GCC. struct S { pthread_mutex_t mutex;

It depends, of course, what operating system you have installed on the RPi, but given that it's an ARM1176JZFS (ARMv6) chip, I would expect to see armv6, not armv4t, in the CPU part of the triple. It has a VFP unit, so I'd assume that you'd want to set hardfp (unless you installed an OS that doesn't support hardfp in its standard library), but if ld is complaining then you almost

On 25 March 2016 at 04:11, Hal Finkel <hfinkel at anl.gov> wrote: > As I understand it, the fundamental property being addresses here is: Are the semantics of scalar FP math the same as vector FP math? TTI seems like a good place to expose that information. If the semantics are indeed different, then the vectorizer would require fast-math flags in order to vectorize FP operations

Hello, I asked here for kind of reference GCC version which LLVM development team is using for *native* testing on ARM hardware. (no cross compilation!) last week or so. I've been curious myself how the situation looks and so I tested LLVM 2.9 as a reference point and LLVM HEAD as of June 29 on ARMv7 (two boards with two different Ubuntu versions) compiled by GCC 4.3.4, 4.4.1, 4.4.5,

On Tue, Sep 11, 2012 at 04:45:23AM +0200, Óscar Fuentes wrote: > "陳韋任 (Wei-Ren Chen)" <chenwj at iis.sinica.edu.tw> writes: > > > I have been stuck on compiling LLVM/Clang (r163485) on pandaboard which has > > following configuration, > > > > - Ubuntu 11.04 + 1G Mem + 1G Swap + 32G SD card > > - GCC 4.5.2 > > - GNU gold (GNU

> Chandler’s complex arithmetic changes are also in the range: r219557 in clang. We saw it change the code in mandel-2 significantly. mandel-2 is broken on hard FP ABI systems, btw. The reason is simply: we're emitting a call to __muldc3 with AAPCS VFP calling convention, however, the function expects softfp (AAPCS) calling conv and reads garbage from GP registers. I'm working on fix.

Hi Chris, > The right place to implement this is in lib/Support/Host.cpp. X86 has an implementation of sys::getHostCPUName(), but everything else just uses the: > > std::string sys::getHostCPUName() { > return "generic"; > } > > implementation. I tried to let it return "armv7l" or "cortex-a9" on pandaboard, but the bitcode output by clang

Hi, all It seems that rev. 131463 [1] makes LLVM failed to recognize ARM correctly. My best guess is the variable LLVM_HOSTTRIPLE got something like "armv7l-unknown-linux-gnueabi" when LLVM compiled natively on ARM. Then the Arch (armv7l) is not recognized by LLVM. As you can see from attach (llvm-131463-gcc-4.4.1-native-arm2.log), there are a lot failure while running test cases

thanks - this has been fun. There is one other thing I have been having trouble with - and i've tried it on two archlinuxarm installs and gotten the same thing. i am not even sure if its important for me. but if i try to configure and make with neon support - it cant find the neon libraries. despite neon having been installed several different ways (i tried pacman, as well as compiling

Hi all, I am following the README.arm from Simon to cross compile linphone from my PC to an arm architecture. But i encounter problems about the ogg header. I have this following error when i write this line : ./configure --prefix=/usr --host=arm-linux --with-gnu-ld --disable-static --enable-fixed-point --enable-arm-asm the error is : . . make[2]: entrant dans le r?pertoire ?

2) For lag in execution time due to floating point operations, it was clearly observed that gcc used floating point instruction FSQRT, where as clang seemed to use emulated function (?) BL SQRT. Note that we used the following flags for both clang as well as gcc compilation. -march=armv7-a -mfloat-abi=softfp -mfpu=vfpv3-d16 -mtune=cortex-a8 Infact, i was surprised to see that even when

On 3 July 2011 21:32, Karel Gardas <karel.gardas at centrum.cz> wrote: > please see http://ghcarm.wordpress.com/2011/07/03/llvm-on-arm-testing/ > > Is there anything other I might do for you to get those regressions fixed? Hi Karel, This is great! I can see there's only a handful of errors. All JIT errors seem to be the same (MC). All O2 errors, too (MIPS). The select.ll