search for: hardfloat

...Gentoo machine): > horus /etc/portage # named -V > BIND 9.11.3 (Extended Support Version) <id:a375815> > running on Linux armv7l 4.4.136-695e41116993e0a4f080354e72f13d91-0 #1 > SMP Thu Jun 14 14:09:46 CEST 2018 > built by make with '--prefix=/usr' '--build=armv7a-hardfloat-linux-gnueabi' > '--host=armv7a-hardfloat-linux-gnueabi' '--mandir=/usr/share/man' > '--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc' > '--localstatedir=/var/lib' '--libdir=/usr/lib' '--sysconfdir=/etc...

...rom being merged together. For example, `-msoft-float' changes the calling convention in the output file. Therefore, it's only useful if the whole program is compiled with it. It would be a module-level IR flag: It seems that the correct solution for this would be to make the softfloat and hardfloat calling conventions into... calling conventions. This would require sinking some logic for defining calling conventions down into LLVM, rather than requiring every single front end to duplicate the same logic, but reduced code duplication might just be a price worth paying for making writing front...

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?

...unning into a requirement to do this again: while it's much less crashy than it was, I still can't seem to persuade the JIT to generate hard-float code. This is with LLVM 3.3, 3.4 and 3.5. I'm using MCJIT (although I've tried without, as well), and I've tried setting FloatABI to HardFloat. Does anyone know if this is actually working yet? If so, are there any examples of how to do this successfully? -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ "Feminism encourages women to leave their husbands, kill their │ children, practice withcraft, destroy capitalism and...

...over wrote: [...] > It looks like it's a case of calling Module::setTargetTriple. As with > most JIT setup questions, though, often the best way to find out is to > get something working in lli and then look at what it does > (tools/lli/lli.cpp). Well, it's *almost* working --- hardfloat code is now being generated, and it even seems to be right most of the time! Unfortunately it looks like it's getting calling conventions wrong. This IR code: define void @Entrypoint(float %in, float* %out) { store float %in, float* %out } ...gets compiled to this: STRi12 %R0<kill&gt...

...eholder will be replaced with the appropriate value at the test run time. For example, if the test/CodeGen/Generic/2003-07-07-BadLongConst.ll will be defined as ; RUN: llc -march=$each_target < %s it will be executed as llc -march=arm  < /opt/test-buildslave/osuosl/slave/build-x-4-armeabi-hardfloat/llvm.src/test/CodeGen/Generic/2003-07-07-BadLongConst.ll llc -march=thumb  < /opt/test-buildslave/osuosl/slave/build-x-4-armeabi-hardfloat/llvm.src/test/CodeGen/Generic/2003-07-07-BadLongConst.ll for llvm configured with --enable-targets=arm. Note that $each_target and targets/llvm_supports_ta...

...c to emit a list of what triples they support? Since I posted my message I notice that clang 3.2 has hit Debian experimental. This no longer produces the warning about an unrecognised platform, but it still generates softfloat code --- I've compared clang's output and gcc, and gcc produces hardfloat code. (Incidentally, I was wrong earlier about clang 3.2 failing. Its output causes ld to produce an assertion message, and it didn't occur to me then to look to see whether it had actually created a binary or not.) Here's what clang 3.2 says with 'clang -v -S -O3 test.c': Debian...

...ing 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: 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? > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiu...

On 7/23/14, 1:20 PM, Tim Northover wrote: [...] > You should probably be specifying a triple directly, and making it an > AAPCS-VFP one for good measure: "armv7-linux-gnueabihf" for example, > or "thumbv7-none-eabihf". You shouldn't even need to set FloatABI for > those two. How do I do this? (I can't find any examples, and the API is decidedly unclear...)

> 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 8 February 2013 21:42, David Given <dg at cowlark.com> wrote: > The box itself is an Allwinner A10; armv7l. /proc/cpuinfo says it's got > swp half thumb fastmult vfp edsp neon vfpv3. > Yes, it's a Cortex-A8. I've been unable to find any values for CPU which are accepted (it just > says 'unknown target CPU'. I've tried arm, armv7, armv7a, armv7l,

Hello, I've built LLVM natively on a fpu-less (soft-float) mips32 target, and built mesa to use it. However llvm apparently cannot determine what machine it's running on and builds code for a generic mips target with fpu. Is there a way to have llc/llvm always use "-march=mipsle -mcpu=mips32 -mattr=+soft-float" as a default command line, something similar to gcc's

...stribution from scratch using these compilers. From a sysroot layout point of view there will be folders called mips64el-linux-gnu in various places albeit the libraries in each will have wildly different ABIs. For 1) When I run gcc I get n64+softfloat+nan2008+i6400 For 2) When I run gcc I get n32+hardfloat+doublefloat+nan2008+i6400 For 1) when I run gcc -mabi=32 I get o32+soft-float+nan2008+i6400 For 2) when I run gcc -mabi=32 I get o32+hardfloat+doublefloat+nan2008+fpxx+i6400 If I want to use clang as simply as I use GCC what do I need to change in llvm/clang to create a compiler such that I can r...

...l agree that this is an acceptable approach to take and that it's no different from how other targets handle certain ABI's and how we already handle -m32/-m64/-EL/-EB/etc. The approach I'm using is to encode the ABI information into the triple in the same way that ARM does for EABI and hardfloat, and the same way that X86 does for X32. These targets define variants of Triple::GNU for each of these ABI's in the form of the Triple::GNUEABI, Triple::GNUEABIHF, and Triple::GNUX32 values of the environment component of the triple and it's up to the frontend and/or API-user to pass the r...

On 8 February 2013 14:28, David Given <dg at cowlark.com> wrote: > Debian's clang packages are totally broken on armhf --- the compiler > emits a confused warning about the platform being unrecognised, and then > generates softfloat code --- so I was wondering about LLVM itself. I'm using Ubuntu on Pandas and Chromebooks and LLVM itself behaves well, with the right set of

Hi, Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should use library calls for floating point. And that's only the tip of the proverbial iceberg. Goals ===== My goals for whichever solution we come up with are

...l agree that this is an acceptable approach to take and that it's no different from how other targets handle certain ABI's and how we already handle -m32/-m64/-EL/-EB/etc. The approach I'm using is to encode the ABI information into the triple in the same way that ARM does for EABI and hardfloat, and the same way that X86 does for X32. These targets define variants of Triple::GNU for each of these ABI's in the form of the Triple::GNUEABI, Triple::GNUEABIHF, and Triple::GNUX32 values of the environment component of the triple and it's up to the frontend and/or API-user to pass the r...

Renato Golin wrote: [...] > Try setting armv7a-unknown-linux-gnueabihf and see if it works better. No, that doesn't work either. [...] > JIT was never the forte of ARM and I haven't tried yet, but I doubt > it'll be any Debian misconfiguration. The whole architecture > configuration is a bit odd... Debian's clang packages are totally broken on armhf --- the compiler

...s such as clang, or API's such as Target::createTargetMachine() will always get the defaults corresponding to the triple. These defaults, as we discussed above vary according to the OS (MIPS-II on Debian, MIPS32R2 on Fedora). This kind of problem also exists in other forms such as Softfloat vs Hardfloat defaults, NAN1985 vs NAN2008 defaults, default ABIs, etc. Other things to mention MIPS64 is not a fundamentally different architecture from MIPS32. If we had a representation of the ABI in the triple then we wouldn't need Triple::mips64/mips64el. From: Eric Christopher [mailto:echristo at gm...

Hi, I found the main reason for sound distortions on my system is guest timer configuration. The working one is: <clock offset="localtime"> <timer name="hypervclock" present="yes"/> <timer name="hpet" present="no"/> <timer name="rtc" present="yes" track="guest"