search for: armv7a

...JITTest.AvailableExternallyGlobalIsntEmitted LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.FunctionPointersOutliveTheirCreator Expected Passes : 3239 Expected Failures : 46 Unsupported Tests : 2352 Unexpected Failures: 7 $ gcc -v Using built-in specs. COLLECT_GCC=/usr/armv7a-unknown-linux-gnueabi/gcc-bin/4.5.3/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/armv7a-unknown-linux-gnueabi/4.5.3/lto-wrapper Target: armv7a-unknown-linux-gnueabi Configured with: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/configure --prefix=/usr --bindir=/usr/armv7a-unknown-linux-gnueabi...

Motivation At the moment, when targeting armv7a, clang defaults to generate code as if -mcpu=cortex-a8 was specified. When targeting armv8a, it defaults to generate code as if -mcpu=cortex-a53 was specified. This leads to surprising code generation, by the compiler optimizing for a specific micro-architecture, whereas the intent from the user w...

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,

...results! Android is definitely in favor of fixing the defaults, so this proposal looks great from our perspective. Thanks, Steve On Wed, May 31, 2017 at 5:57 AM, Kristof Beyls <Kristof.Beyls at arm.com<mailto:Kristof.Beyls at arm.com>> wrote: Motivation At the moment, when targeting armv7a, clang defaults to generate code as if -mcpu=cortex-a8 was specified. When targeting armv8a, it defaults to generate code as if -mcpu=cortex-a53 was specified. This leads to surprising code generation, by the compiler optimizing for a specific micro-architecture, whereas the intent from the user w...

...uot;armv7b" also exists. As do "armv6l", "armv6b" and probably "armv8" equivalents too if you ran a 32-bit kernel there. Adding random aliasing on an ad-hoc basis doesn't scale or represent what's really going on. > In the Arch side, ARMv7l is *really* ARMv7A, so it should not have any > further knowledge about the rest of the environment. What does RTLinux on an R-class CPU present itself as? My guess would be "armv7l" too. I'm not too concerned about deciding that we only care about A-class Linux, but I am concerned about taking an u...

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 using LLVM from the git mirror: $ lli -version LL...

...[1], I am trying to target the ARM on the Zedboard [2]. It is an ARM Cortex-A9. The machine I am compiling on is an x86_64 Fedora Linux machine, using clang 3.3. I am failing to generate an executable, instead seeing an error "unrecognized option '-mfpu=neon'". $ clang -v -target armv7a-linux-eabi -mcpu=cortex-a9 -mfloat-abi=soft -mfpu=neon helloworld.c clang version 3.3 (tags/RELEASE_33/rc3) Target: armv7a--linux-eabi Thread model: posix "/usr/bin/clang" -cc1 -triple armv7--linux-eabi -S -disable-free -disable-llvm-verifier -main-file-name helloworld.c -mrelocation-mod...

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 <tom at stellard.net> wrot...

On 26 November 2013 15:36, Rob Stewart <robstewart57 at gmail.com> wrote: > $ clang -v -target armv7a-linux-eabi -mcpu=cortex-a9 -mfloat-abi=soft > -mfpu=neon helloworld.c > Hi Rod, You need cross-binutils installed on your box. If you use Debian, there are packages (gcc-4.7-arm-linux-gnueabi and friends). Other distros may have similar packages, but you can always download the Linaro toolc...

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 using LLVM from the git mirror: $ lli -version LL...

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 -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 using LL...

...VT::i64 properly on arm errors http://labb.zafena.se/shark-testing/llvmARMCodeGenFailures200904/i64armLoweringRelatedErrors/ example: root at overo:/home/xerxes/llvm-test/fail/CodeGen/notnativelysupported# llvm-as < 2008-02-04-ExtractSubvector.ll | llc llc: /usr/src/openembedded/overo/tmp/work/armv7a-angstrom-linux-gnueabi/llvm2.6-2.6-r0/llvm-2.6/include/llvm/Target/TargetLowering.h:158: llvm::TargetRegisterClass* llvm::TargetLowering::getRegClassFor(llvm::MVT) const: Assertion `RC && "This value type is not natively supported!"' failed. Stack dump: 0. Program arguments: l...

...gt;> 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 not as an architecture variant. >>> However, because the DefaultTargetTriple is armv6l-unknown-linux-gnueabihf Where is this "armv6l" coming from? Is it a legacy GNU thing? Or is it a n...

...MAKE_INSTALL_PREFIX=/home/iiita/crossbuild/build -DLLVM_TABLEGEN=/home/iiita/llvm-3.8/build/bin/llvm-tblgen -DCLANG_TABLEGEN=/home/iiita/llvm-3.8/build/bin/clang-tblgen -DLLVM_DEFAULT_TARGET_TRIPLE=arm-linux-gnueabihf -DLLVM_TARGET_ARCH=ARM -DLLVM_TARGETS_TO_BUILD=ARM -DCMAKE_CXX_FLAGS='-target armv7a-linux-gnueabihf -mcpu=cortex-a9 -I/usr/arm-linux-gnueabihf/include/c++/4.7.3/arm-linux-gnueabihf/ -I/usr/arm-linux-gnueabihf/include/ -mfloat-abi=hard -ccc-gcc-name arm-linux-gnueabihf-gcc' *Error message:* CMake Error at cmake/modules/CheckAtomic.cmake:33 (message): Host compiler must suppo...

...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` 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 using...

...GEN=/home/lab/workspace/llvm/build4x86/bin/llvm-tblgen >> -DCLANG_TABLEGEN=/home/lab/workspace/llvm/build4x86/bin/clang-tblgen >> -DLLVM_DEFAULT_TARGET_TRIPLE=arm-linux-gnueabihf >> -DLLVM_TARGET_ARCH=ARM >> -DLLVM_TARGETS_TO_BUILD=ARM >> -DCMAKE_CXX_FLAGS='-target armv7a-linux-gnueabihf -mcpu=cortex-a9 >> -I/usr/arm-linux-gnueabihf/include/c++/4.7.3/arm-linux-gnueabihf/ >> -I/usr/arm-linux-gnueabihf/include/ >> -I/home/lab/workspace/llvm/llvm-source-code/lib4arm/ >> -I/home/lab/workspace/llvm/llvm-source-code/lib2ubuntu/ >> -I/usr/lib/...

Hello, clang/llvm 4.0.0 generates invalid calls for builtin functions with -mfloat-abi=hard -ffast-math. Small example fail.c: // clang -O2 -target armv7a-none-none-eabi -mfloat-abi=hard -ffast-math -S fail.c -o - extern float sinf (float x); float sin1 (float x) {return (sinf (x));} generates code to pass the parameter in r0 and expect the result in r0. The same code without -ffast-math compiles correctly. It also works with -fno-builtin-...

...s. There is at least a 10 fold increase in the smbd compared to native x86. --- Native x86 ---- -rwxr-xr-x 1 pranavd users 92979 May 31 10:57 /usr/sbin/smbd -rwxr-xr-x 1 pranavd users 351196 May 31 10:57 /usr/sbin/nmbd --- Cross Compiled ---- -rwxr-xr-x 2 pranavd users 9624696 May 30 18:11 /work/armv7a-vfp-neon-oe-linux-gnueabi/samba-4.0.6-r8/packages-split/samba/usr/sbin/smbd -rwxr-xr-x 2 pranavd users 6020020 May 30 18:11 /work/armv7a-vfp-neon-oe-linux-gnueabi/samba-4.0.6-r8/packages-split/samba/usr/sbin/nmbd Can someone please suggest me how to reduce the size of the binaries? I have included...

...ftenfloat_Do_not_know_how_to_soften_the_result_of_this_operator/ > example: > > root at overo:/home/xerxes/llvm-test/fail/CodeGen/softenfloat# llvm-as < 2007-11-19-VectorSplitting.ll | llc > SoftenFloatResult #0: 0x614e00: f32 = undef > llc: /usr/src/openembedded/overo/tmp/work/armv7a-angstrom-linux-gnueabi/llvm2.6-2.6-r0/llvm-2.6/lib/CodeGen/SelectionDAG/LegalizeFloatTypes.cpp:54: void llvm::DAGTypeLegalizer::SoftenFloatResult(llvm::SDNode*, unsigned int): Assertion `0 && "Do not know how to soften the result of this operator!"' failed. > Stack dump: &g...

...g a final link step without a cpu is >> likely to be quite common so I don't think that this will be a corner >> case. >> - The Build Attributes of the output ELF file get the triple ARMv4t >> from -mcpu=arm7tdmi which is lying to the linker as the file contains >> ARMv7a instructions. > > > Having ARMv7a instructions in an ARMv4t file shouldn't be a problem: a > function should be allowed to override the CPU attributes to generate code > for a newer target. This is generally done using the "target" function > attribute. If this doe...