similar to: [LLVMdev] Looking for precompiled compiler-rt for ARM with VFP

The implementation of an float ordered <= looks buggy, but maybe I'm not reading the assembly right. This is lesf2vfp.S in compiler-rt, and it has this code: // extern int __lesf2vfp(float a, float b); // // Returns one iff a <= b and neither is NaN. // Uses Darwin calling convention where single precision arguments are passsed // like 32-bit ints //

On 8 April 2010 02:28, Rodolph Perfetta <rodolph.perfetta at arm.com> wrote: > movhi means mov if unsigned Higher > > movls means mov if unsigned Lower or Same > > > > so depending on the comparison result r0 holds 1 or 0 > Thanks. Now that I understand the assembly, I think there's another problem. libgcc's definition of lesf2 is actually

On 3 February 2011 10:25, Siarhei Siamashka <siarhei.siamashka at gmail.com> wrote: > I have submitted a bug some time ago to LLVM bugtracker: > http://llvm.org/bugs/show_bug.cgi?id=8931 Hi Siarhei, This is a really silly bug with a simple fix. We have a similar patch here locally, but as this is part of another set of patches we were waiting for it to stabilise. There are some

On 27 May 2011 02:04, David Dunkle <ddunkle at arxan.com> wrote: > In all cases, I get code that looks pretty very the same; its like what > is below. However, I am expecting to see instruction level differences > between the vfp3 and neon versions. When I do the same with gcc 4.2 I do > see differences in the generated code. Hi David, You could see different instructions (as

How do I cross-compile compiler-rt for ARM-Linux with CMake? Given a directory with sub-directories named 'llvm', 'compiler-rt', and 'release' (which is a clang build directory), this build succeeds: $ mkdir -p release-rt $ cd release-rt $ cmake ../llvm -G Ninja \ -DCMAKE_INSTALL_PREFIX=ship \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_ENABLE_ASSERTIONS=ON \

On Wed, Dec 18, 2013 at 2:30 AM, Greg Fitzgerald <garious at gmail.com> wrote: >> Not that I know of, and I always build compiler-rt natively, together with Clang and LLVM. :( > > Do you mean "natively on ARM" or "natively on X86 with the ARM target enabled"? > > If the former, do you have a script to merge the target libs into the > host's

I'm using Clang, with arm-none-linux-gnueabi-g++ as a linker. Although compiler-rt replaced libgcc, we still need other libs such as libc, libm, etc. It seems libc is calling these missing functions. > > On Nov 15, 2012, at 9:33 PM, liangh at codeaurora.org wrote: >> I'm trying to link my objs with compiler-rt built runtime lib for arm. >> According to the compiler-rt

Hi Siarhei, I've got the patch in my hands, sorry for the delay. It takes into account the MC emitting the .fpu when in ASM mode and the build attributes in both ASM and ELF mode. Jason, that's the patch I was talking about today. It's non-invasive and I'll send it no later than Monday, so should be in for the 2.9 release. cheers, --renato

Hi guys, Thanks for all the info. Then, if, besides compiler-rt, I also need some other libs, such as libm, how do I link? Here is an example of missing functions in compiler-rt when linking: "-lstdc++ -lm --start-group -lcompiler-rt-armv7 -lgcc_eh -lc --end-group" vs. "-lstdc++ -lm --start-group -lgcc -lgcc_eh -lc --end-group" ...

On Nov 15, 2012, at 9:33 PM, liangh at codeaurora.org wrote: > I'm trying to link my objs with compiler-rt built runtime lib for arm. > According to the compiler-rt doc, it should be able to replace libgcc. > However, if I replace "-lgcc" with "compiler-rt.a" for a static linking, > gcc linker complains about undefined functions. Using "nm -g", I

On 27 May 2011 19:47, Jim Grosbach <grosbach at apple.com> wrote: > Not exactly. The distinction is clear, it's just not expressed as an > either/or question. Specifically, the code generator considers NEON to be a > proper superset of VFP3. So if it has only VFP3, that's all it will use. If > it has NEON, it assumes it also has VFP3 and can use either. Indeed. >

On Friday 25 February 2011 22:28:14 Jason Kim wrote: > On Fri, Feb 25, 2011 at 12:16 PM, Siarhei Siamashka > > <siarhei.siamashka at gmail.com> wrote: > > On Thursday 03 February 2011 14:14:28 Renato Golin wrote: > >> On 3 February 2011 10:25, Siarhei Siamashka > >> <siarhei.siamashka at gmail.com> > > > > wrote: > >> > I have

Hi, I have submitted a bug some time ago to LLVM bugtracker: http://llvm.org/bugs/show_bug.cgi?id=8931 The problem is that I'm trying to use clang in linux system, running on ARM hardware. And this bug, as trivial as it is, seems to be a major showstopper. I wonder if I'm the only one trying to use LLVM/clang in this configuration or doing something in an unusual way? Anyway, the LLVM

Hi Daniel, I'm trying to use the feature you added to Clang a long time ago (2011), the --rtlib=compiler-rt and it doesn't seem to do anything. Now that I have compiler-rt building on ARM and the archive libraries under /lib, I'd like to replace -lgcc with -lclang_rt, but this command line: $ clang --rtlib=compiler-rt -Wl,-lclang_rt foo.c Gives me the warning/errors: clang-3.5:

Evgeniy, I'm getting this error while building on ARM: clang (LLVM option parsing): Unknown command line argument '-asan-instrument-assembly'. Try: 'clang (LLVM option parsing) -help' clang (LLVM option parsing): Did you mean '-asan-instrument-atomics'? [6/32] Generating ASAN_INST_TEST_OBJECTS.asan_asm_test.cc.arm-inline.o This doesn't happen on x86_64, so

> I'm using Clang, with arm-none-linux-gnueabi-g++ as a linker. Although > compiler-rt replaced libgcc, we still need other libs such as libc, libm, > etc. It seems libc is calling these missing functions. If you compile libc with gcc, then yes, you might need arbitrary functions from libgcc. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint

On 20 December 2013 10:43, Alexey Samsonov <samsonov at google.com> wrote: > There are simply no CMake build rules for building compiler-rt > libraries targeting ARM (see compiler-rt/lib/CMakeLists.txt). > Hi Alexey, I've added the ARM files on that CMake file but I got nothing compiled on ARM. Am I missing something? About the sanitizers, is there anyone that is known to

On May 27, 2011, at 10:49 AM, David Dunkle wrote: > Thanks, that helps a lot. > >> All chips (to date) with NEON have VFP3, so it's safe to assume that a > -mfpu=neon will have VFP3, so all the decisions >> about code generated for VFP3 can safely be assumed by targets with > NEON. > > Just to confirm my understanding, can I correctly say in general that >

On 8 July 2014 19:47, Alexey Samsonov <vonosmas at gmail.com> wrote: > compiler-rt/lib/builtins/arm/*.S files are listed in arm_SOURCES variable, > and therefore should make it into the builtins static library on ARM. Don't > they? I assume so... But I'm not an expert in CMake.

Hi, I'm trying to link my objs with compiler-rt built runtime lib for arm. According to the compiler-rt doc, it should be able to replace libgcc. However, if I replace "-lgcc" with "compiler-rt.a" for a static linking, gcc linker complains about undefined functions. Using "nm -g", I compared the functions in libgcc and compiler-rt.full-arm.a and found there are