similar to: [LLVMdev] lli supports different targets than llc?

Hi, Is it normal/expected for `llc` to support a different set of targets than `lli`? I have a hello.ll on which this works: $ llc -mtriple=armv7a-linux-gnueabihf hello.ll # OK, generates hello.s But this doesn't: $ lli -mtriple=armv7a-linux-gnueabihf hello.ll # lli: error creating EE: No available targets are compatible with this triple, see -version for the available targets. I'm

s/pretty much/definitely/ Even then, “works” is too strong a word. Caveat emptor and all that. > On Jul 23, 2015, at 1:20 PM, Eric Christopher <echristo at gmail.com> wrote: > > > > On Thu, Jul 23, 2015 at 10:31 AM Débora Setton Sanches <setton.debora at gmail.com <mailto:setton.debora at gmail.com>> wrote: > Hi, > > Is it normal/expected for `llc`

On Thu, Jul 23, 2015 at 10:31 AM Débora Setton Sanches < setton.debora at gmail.com> wrote: > Hi, > > Is it normal/expected for `llc` to support a different set of targets > than `lli`? > I have a hello.ll on which this works: > > $ llc -mtriple=armv7a-linux-gnueabihf hello.ll > # OK, generates hello.s > > But this doesn't: > > $ lli

But I am running it on the host, as a kind of intermediate step in the cross-compilation, just to check if everything still works after the frontend step. Shouldn't it work then? I don't know much about how everything works yet, sorry if it's a silly question. What I thought was also weird is that the exact same example works if I use the OpenMP/Clang fork

Hi, You're asking lli to create a JIT for ARM code on an Intel platform... That's not realistically going to be achievable :) Cross compilation is easy, cross execution requires an emulator. Cheers, James On Mon, 27 Jul 2015 at 23:13, Débora Setton Fernandes <debora.setton at usp.br> wrote: > Hi, > > Is it normal/expected for `llc` to support a different set of targets

Hi, Is it normal/expected for `llc` to support a different set of targets than `lli`? I have a hello.ll on which this works: $ llc -mtriple=armv7a-linux-gnueabihf hello.ll # OK, generates hello.s But this doesn't: $ lli -mtriple=armv7a-linux-gnueabihf hello.ll # lli: error creating EE: No available targets are compatible with this triple, see -version for the available targets. I'm

Hi all, I'm organizing a BoF session during the upcoming EuroLLVM developers meeting. As the subject of this message already shows, this session will be on compilers in education. I'm currently looking for both participants to the discussion and input for the actual program of the session. I've already got some ideas which I'll introduce below. At our university, we mostly

>> Going back through SVN history, I cannot find any evidence that ARMv6L ever existed. > > Oh, my bad!! I was thinking of ARMv7l... :/ > > Nevertheless, I'll leave you guys to review this one, as I lost touch with the parser a while ago. Ah, I see: ARMv7L is now an alias for ARMv7A. So, if William has to add support for ARMv6L, I'd suggest he adds it as an alias, and

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,

Hi renato, 1. The command above is followed by the guide[ HowToCrossCompileLLVM.rst ] and I specify some path(ex. <path-to-host-bin>). 2. The including x86_64 libraries is added because of some missing libraries(ex. "error: Host compiler appears to require libatomic, but cannot find it"). As I have found that the bugs needed to dealt with is some ARM-dependent libraries, I

Hello All, I am building llvm-clang cross tool chain for arm target, after successful build for Linux host now I am now building toolchain for *arm target*. However, I am getting below error message which seems to be confusing and not getting any idea how to resolve this issue. *Command :* #CC='clang' CXX='clang++' cmake -G Ninja /home/iiita/crossbuild/llvm

Hi Tom, When running the test script, I got an error message: $ ./test-release.sh -no-64bit -release 3.4.2 -rc 1 -triple armv7a-linux-gnueabihf -j2 # Validating llvm SVN URL llvm 3.4.2 release candidate rc1 doesn't exist! Do I need to get another test-release.sh script? This is the one from release_34 branch we used to release 3.4.1. cheers, --renato On 16 May 2014 22:55, Tom Stellard

Hello All, I am building llvm-clang tool chain for *arm target* by following the steps from http://clang.llvm.org/docs/CrossCompilation.html *However when I tried following cmake command for build tool chain it gives the error message :* #CC='clang' CXX='clang++' cmake -G Ninja /home/iiita/llvm-exp/llvm -DCMAKE_CROSSCOMPILING=True

On 8 February 2013 11:01, David Given <dg at cowlark.com> wrote: > I've tried overriding the triple to arm-unknown-linux-gnueabihf and > arm-linux-gnueabihf (via module->setTargetTriple), and while the triples > are accepted, the actual generated code doesn't change with either. > Hi David, If you set the triple to arm it won't help, since it'll default to

Dear Samba experts, Since a couple of days I am trying to fix my domain. I have each two ADDCs on raspis on two sites. One is running on Raspian and works fine. The other three are on Gentoo and something is broken there. When I point the name resolution in resolv.conf to the Raspian machine the dynamic updates are just working fine: # horus /srv/samba/demoshare # samba_dnsupdate --verbose

Hi Hans, we have uploaded tarballs for ARM and AArch64 targets: a20ea3fe482e754a61ccb37c67456ad1 clang+llvm-6.0.1-aarch64-linux-gnu.tar.xz f37b132c3dfb3b776524980be5af3a76 clang+llvm-6.0.1-armv7a-linux-gnueabihf.tar.xz and 47a9a9bb02d41581e6804b98918188f6 clang+llvm-7.0.0-aarch64-linux-gnu.tar.xz e639d8f5dc58be5cf44d017fd5eefd6c clang+llvm-7.0.0-armv7a-linux-gnueabihf.tar.xz Yvan On Mon,

On 08/02/13 14:42, Renato Golin wrote: [...] > Can you paste the result of a "clang -v -mcpu=CPU file.c" on your box? I > want to see what are the arguments and the assembler/linker it's > choosing to use. What CPU are we talking about? The box itself is an Allwinner A10; armv7l. /proc/cpuinfo says it's got swp half thumb fastmult vfp edsp neon vfpv3. I've been

On 13 December 2016 at 22:10, Tom Stellard via cfe-dev <cfe-dev at lists.llvm.org> wrote: > I've created the 3.9.1-final tag no changes from -rc3. Testers can > begin uploading binaries now. ARMv7 done, all good. sha1sum: 0dd35c771750c6fbfccda1d32b10207f336a12bc clang+llvm-3.9.1-armv7a-linux-gnueabihf.tar.xz cheers, --renato

Hello Peter and Lists, thanks a lot, that way it worked out! The final cmake was cmake -G "Ninja" ../llvm/projects/compiler-rt/ -DCOMPILER_RT_BUILD_BUILTINS=ON -DCOMPILER_RT_BUILD_SANITIZERS=OFF -DCOMPILER_RT_BUILD_XRAY=OFF -DCOMPILER_RT_BUILD_LIBFUZZER=OFF -DCOMPILER_RT_BUILD_PROFILE=OFF -DCMAKE_C_COMPILER=/usr/local/myclang/bin/clang -DCMAKE_AR=/usr/local/myclang/bin/llvm-ar

Hello list, I have some problems using LLVM version 3.8.0 to cross-compile code for ARM Cortex-A9 on x86. I am trying to generate LLVM IR using Clang: clang -S --emit-llvm --target=armv7a-linux-gnueabihf --sysroot=$(ARM_SYSROOT) --gcc-toolchain=$(ARM_GCC_TOOLCHAIN) -c -o translated.ll But somehow clang it is trying to use soft-float and I get the following error: 'gnu/stubs-soft.h' file