search for: hardfp

Displaying 10 results from an estimated 10 matches for "hardfp".

Did you mean: hard
2012 Apr 15
3
[LLVMdev] About LLVM 3.1 ARM testing
> 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...
2012 Apr 15
0
[LLVMdev] About LLVM 3.1 ARM testing
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 a cross compiler with hardfp enabled to compile...
2012 Dec 30
2
[LLVMdev] Targetting the raspberry pi
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?
2012 Dec 30
0
[LLVMdev] Targetting the raspberry pi
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 certainly have a mismatch. David On 30 Dec 2012, at 10:42, Carlo Kok wrote: > Targetting the raspberry pi, what triple/flags should I set? > > I tried triple:...
2012 Apr 14
0
[LLVMdev] About LLVM 3.1 ARM testing
...precious time. As > discussed > on the ML before, I plan to cross compile LLVM/Clang first, then run > regression > test and test suite on the pandaboards. Could someone help me check to see > if I > miss something? Thanks! > Ubuntu on ARM is softfp, right? How about testing hardfp with a distribution like ArchLinuxArm? > Here is the pandaboard configuration, > > --- > $ uname -a > Linux arm2 2.6.38-1208-omap4 #11-Ubuntu SMP PREEMPT Fri Apr 15 16:34:35 > UTC 2011 armv7l armv7l armv7l GNU/Linux > $ gcc -v > gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubu...
2012 Apr 14
2
[LLVMdev] About LLVM 3.1 ARM testing
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 the pandaboards. Could someone help me check to see if I miss something? Thanks! Here is the pandaboard configuration,
2011 Jan 23
0
[LLVMdev] Target Triple Changes
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
2013 Jun 04
1
[LLVMdev] MCJIT and Kaleidoscope Tutorial
Hi Dmitri, You're right. The lli code should be cleaned up. As David said, there was a time when the call to invalidate the instruction cache was necessary. It isn't necessary anymore. -Andy -----Original Message----- From: Dmitri Rubinstein [mailto:dmitri.rubinstein at googlemail.com] Sent: Tuesday, June 04, 2013 7:20 AM To: David Tweed Cc: Kaylor, Andrew; LLVM Dev Subject: Re:
2011 Jan 22
2
[LLVMdev] Target Triple Changes
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
2015 Mar 02
13
Patch cleaning up Opus x86 intrinsics configury
The attached patch cleans up Opus's x86 intrinsics configury. It: * Makes ?enable-intrinsics work with clang and other non-GCC compilers * Enables RTCD for the floating-point-mode SSE code in Celt. * Disables use of RTCD in cases where the compiler targets an instruction set by default. * Enables the SSE4.1 Silk optimizations that apply to the common parts of Silk when Opus is built in