search for: armv6

...-darwin --enable-targets=x86,x86_64,cbe --enable-optimized $ make $ make install It will eventually error out with: /Users/erickt/Projects/llvm/gcc-i386/llvm-build-Release/Release+Asserts/bin/clang -no-integrated-as -ccc-install-dir /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/ -arch armv6 -fvisibility=hidden -DVISIBILITY_HIDDEN -mkernel -DKERNEL_USE -Wall -Werror -O3 -fomit-frame-pointer -miphoneos-version-min=1.0 -isysroot /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.3.sdk -mthumb -c -o /Users/erickt/Projects/llvm/gcc-i386/llvm-build-Release/tools/clang/runtime/c...

Hi all. I’ve been working with Swift on ARMv6 and v7. While working with ARMv6 on linux, I noticed that my arm architecture canonicalization code didn’t produce the expected result. The code that I had been using (within Swift’s Driver.cpp the following: static llvm::Triple computeTargetTriple(StringRef DefaultTargetTriple) { llvm::Triple...

Hi, all I want to use LLVM to compile an ARM Cortex-M0 project on windows. Who can send me a sample, including command arguments and introdution about debug process. Thanks a lot. -Steven ***************************** Legal Disclaimer ***************************** "This email may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized

Hi, I was compiling libc++ with a recent TOT (248571) and when I got to the ARMv6, I got a code generation error in memory.cpp: fatal error: error in backend: Cannot select: intrinsic %llvm.arm.clrex ecc: error: clang frontend command failed with exit code 70 (use -v to see invocation) clang version 3.8.0 (trunk) It looks as if the newly added emitAtomicCmpXchgNoStoreLLBalanc...

...ast three development releases in the 0.33 series. Please note that this release doesn't contain any changes since the previous development version (0.33.6) was released. For those who didn't follow the development release announcements, the 0.34 version contains major improvements to ARMv6 and POWER (both BE and LE) architectures, enhancements of tests and utilities and important bug fixes. See below the full git log since the previous major release (0.32). Thanks, Oded tar.gz: http://cairographics.org/releases/pixman-0.34.0.tar.gz http://xorg.freedesktop.org/archive/ind...

...release 0.33.2 is now available. This is a release candidate for a stable 0.34.0 release. This release comes after little more than 1 year since the previous release (0.32.6). Therefore, the git log is quite long and there are multiple changes, fixes and enhancements. The main changes are: - ARMv6 - Many fast paths implementations were added - PPC64/PPC64LE - Fix all outstanding bugs and add many fast paths implementations using vmx - Major enhancements to lowlevel-blt-bench utility - A couple of fixes and enhancements to mmx code As I mentioned above, many more fixes and improvements to v...

Hello, I am trying to build a speex library file for armv6 on intel MAC OS. I've also put -enable-arm5e-asm whether arm5e-asm works or not. ./configure -prefix=/Users/mijin/temp -disable-shared -enable-static - enable-fixed-point -enable-arm5e-asm This gives below errors. gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I.. -g - O2 -...

...Looks like this was caused by r248294. Author CC'ed. > > On Fri, Sep 25, 2015 at 1:46 PM, Richard Pennington via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> >> I was compiling libc++ with a recent TOT (248571) and when I got to the >> ARMv6, I got a code generation error in memory.cpp: >> >> fatal error: error in backend: Cannot select: intrinsic %llvm.arm.clrex >> ecc: error: clang frontend command failed with exit code 70 (use -v to see >> invocation) >> clang version 3.8.0 (trunk) >> >> It...

On Thu, 8 Jan 2015, Jonathan Lennox wrote: > Every armv7 (and armv8) iOS device has supported Neon, and Xcode support for > armv6 was dropped with Xcode 4.5. > > Even if you?re compiling with an old Xcode version to support really old iOS > devices, Apple?s armv6/armv7 selection was a compile-time switch (supported > using fat binaries). ?I think the arch can be detected based on on > preprocessor defines, tho...

This adds run-time CPU detection for iOS devices. I found this page useful for CPU support and models: http://iossupportmatrix.com/ The patch could be simplified to just set the OPUS_CPU_ARM_NEON flag if you think it's unlikely that anyone would be running on the really old devices that don't support NEON. Tom -------------- next part -------------- An HTML attachment was scrubbed...

..., but the warning itself seems unnecessary because both seem to internally expand to "armv5e-unknown-unknown-eabi" in the current format. Something similar happens with iOS targets because they contain a version in the OS part of the string, so multiple warnings are generated about "armv6-apple-ios4.0.0" and "armv6-apple-ios4.0.1" and similar, which isn't really desirable most of the time. Even whether the arm version part of the string matters is kind of questionable given that bitcode for armv6 shouldn't contain anything that would make it fail with armv7,...

On Sep 22, 2011, at 11:47 AM, Valentin Radu wrote: > checking for armv7-apple-darwin-clang... no > checking for armv7-apple-darwin-llvm-gcc... no > checking for armv7-apple-darwin-gcc... no It's because you don't have a compiler around that targets arm by default. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Sep 22, 2011, at 11:51 AM, Eric Christopher wrote: > > On Sep 22, 2011, at 11:47 AM, Valentin Radu wrote: > >> checking for armv7-apple-darwin-clang... no >> checking for armv7-apple-darwin-llvm-gcc... no >> checking for armv7-apple-darwin-gcc... no > > It's because you don't have a compiler around that targets arm by default. Exactly right. You

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?

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 mism...

On Fri, Sep 25, 2015 at 05:34:03PM -0700, JF Bastien via llvm-dev wrote: > In pre-v6 Linux you could use the kernel-provided helpers: > > https://www.kernel.org/doc/Documentation/arm/kernel_user_helpers.txt Please *never* tell people to use those directly. There are kernels other than Linux and the very idea of hardcoding random kernel address should make all red warning lights go off.

On Sun, Sep 27, 2015 at 05:07:17PM -0700, JF Bastien wrote: > It's part of the stable Linux ABI for ARM. Yes there are non-Linux OSes, > and I wasn't suggesting one emit these calls for non-Linux. > > Please clarify the red warning lights. FWIW these functions were used by > Chrome on ARM until very recently, specifically for the sake of older ARM > CPUs. I know. It is

...e beginning of the archive file. It will at least be aligned to two bytes. With most current host architectures handling packed_endian_specific_integral is fairly efficient. For example, on x86_64 reading 32 bits with 1 2 and 4 byte alignment produces in all cases: movl (%rdi), %eax But on armv6 the aligned case is ldr r0, [r0] the 2 byte aligned case is ldrh r1, [r0, #2] ldrh r0, [r0] orr r0, r0, r1, lsl #16 and the unaligned case is ldrb r1, [r0] ldrb r2, [r0, #1] ldrb r3, [r0, #2] ldrb r0, [r0, #3] orr r1, r1, r2, lsl #8 orr r0,...

...pp =================================================================== --- unittests/ADT/TripleTest.cpp (revision 257090) +++ unittests/ADT/TripleTest.cpp (working copy) @@ -851,6 +851,10 @@ EXPECT_EQ("arm1136jf-s", Triple.getARMCPUForArch()); } { + llvm::Triple Triple("armv6l-unknown-eabi"); + EXPECT_EQ("arm1136jf-s", Triple.getARMCPUForArch()); + } + { llvm::Triple Triple("armv6j-unknown-eabi"); EXPECT_EQ("arm1136jf-s", Triple.getARMCPUForArch()); } I looked into the tests (and unit tests), and found that perhaps...

Hello, For the last couple of days I struggled to find a way to compile LLVM with Clang for ARM. Now, I tried many variations of the settings, linkers and compilers, but I was able only to build for i386 and x86_64. My machine is an i386 iMac. This is my first attempt to cross-compile something, so probably I'm doing something incredible stupid. First, I'm not sure which compiler should