similar to: [LLVMdev] How can I cross compile Clang+LLVM-2.7 for Arm Cortex-A8

I place codesourcery toolchain 2010q1 there, but the sh tell me "CodeSourcery tarball not found in /root/tmp/arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 ", does 2007q3 support ARM Cortex A8? What can I do? 2010/5/5 Eli Friedman <eli.friedman at gmail.com> > On Tue, May 4, 2010 at 8:57 PM, 爱好者 <proljc at gmail.com> wrote: > > hi all > >

hi all We want speed up our applications, so we want use llvm-gcc. I nerver cross build it for arm, and I didn't find enough information in llvm docs. Our cpu is cortex a8, anybody tell me how can I do? Step by step. THANK YOU! yours Liu -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello > My host is Linux on x86, and I want llvm-gcc generate code for Arm > Cortex-A8. > I saw that in LLVM 2.7 Release Notes, but I can't find step to build > it. Anyone tell me? Build llvm-gcc exactly the same way you're building the cross gcc for your target. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State

hi My host is Linux on x86, and I want llvm-gcc generate code for Arm Cortex-A8. I saw that in LLVM 2.7 Release Notes, but I can't find step to build it. Anyone tell me? llvm-gcc now has complete support for the ARM v7 NEON instruction set. This support differs slightly from the GCC implementation. Please see the ARM Advanced SIMD (NEON) Intrinsics and Types in LLVM Blog

On Tue, May 4, 2010 at 8:57 PM, 爱好者 <proljc at gmail.com> wrote: > hi all >       We want speed up our applications, so we want use llvm-gcc. I nerver > cross build it for arm, and I didn't find enough information in llvm docs. >       Our cpu is cortex a8, anybody tell me how can I do? Step by step. > THANK YOU! > yours Liu Try the

hi all I use --enable-targets=arm configure LLVM, build it with Clang, but when I using Clang, it say: #clang -triple /root/a.c error: unable to create target: 'No available targets are compatible with this triple, see -version for the available targets.' 1 diagnostic generated. How can I use Clang generate code for ARM Cortex-A8? thank you -------------- next part

Questions about the port of Xen to ARM with virt extensions are best posted to xen-devel, the xen-arm list focuses on the PV port. Adding xen-devel since it seems you are mainly asking about the w/-virt-extensions port. On Fri, 2012-05-18 at 12:38 +0100, Krishna Pavan wrote: > Please inform the status of Xen-ARM for Cortex-A8 CPU''s on FME from > ARM. AFAIK no one has tried the

Thanks for everyone giving their feedback! I saw pretty unanimous support for making -mcpu=generic the default and making -mcpu=generic schedule for an in-order CPU (Cortex-A8 in this case). I'll be making those changes shortly. I think the comments also make clear that it's less obvious whether we'd want -mcpu=native to become a default. It's probably good for some use cases, but

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 was probably to generate code that is

On 2013-10-18 7:11 AM, Sebastian Reimers wrote: > Hello!, > > i've just compared the 1.0.3 release with the master branch > on a BeagleBone Black (AM335x 1GHz ARM Cortex-A8 with NEON > floating-point accelerator) and Arch Linux ARM. > > At the moment I dont no why, but I see that 1.1 is much slower > in encoding. Are there any default changes, that I missed and could

On Fri, Oct 18, 2013 at 2:21 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Just to clear things up... So 1.1 has some new analysis code that > increases the amount of CPU. When building as floating point (which you > appear to be doing, right?), the new code is enabled at complexity 7 and > up (opusenc defaults to complexity 10 IIRC). This is why you've been >

Hi, Just to clear things up... So 1.1 has some new analysis code that increases the amount of CPU. When building as floating point (which you appear to be doing, right?), the new code is enabled at complexity 7 and up (opusenc defaults to complexity 10 IIRC). This is why you've been seeing an increase in the CPU time. In version 1.0.x, complexity 5-10 are the exactly the same for music.

Hello!, i've just compared the 1.0.3 release with the master branch on a BeagleBone Black (AM335x 1GHz ARM Cortex-A8 with NEON floating-point accelerator) and Arch Linux ARM. At the moment I dont no why, but I see that 1.1 is much slower in encoding. Are there any default changes, that I missed and could explain this? Normaly I suggested a better performance with 1.1 and the ARM

On Jul 2, 2009, at 6:24 PM, Neel Nagar wrote: > I suspect that my llvm-gcc cross compiler is using the wrong > assembler because it does not recognize "-mcpu=cortex-a8". This is a known problem. We've only added support for ARMv7 (including cortex-a8) in llvm in the last week or so, and the associated changes for llvm-gcc are still pending. Unless you need specific

Hello, I'm using gold linker now to see if there can be any performance gain. Also using latest gcc version (4.4.4) and latest binutils. But when I'm compiling llvm-gcc, I'm getting this error. /home/jal/llvm-gcc-4.2-2.7.source/host-i686-pc-linux-gnu/gcc/xgcc -B/home/jal/llvm-gcc-4.2-2.7.source/host-i686-pc-linux-gnu/gcc/ -B/usr/local/arm-v7a8-linux-gnueabi/bin/

Hello Anton, Thanks for replying. The message "as: unrecognized option `-mcpu=cortex-a8'" is the same message I get when I just enter: as -mcpu=cortex-a8 So I think I llvm-gcc is using the Linux i386 assembler to assemble ARM code. Not good. What assembler is it supposed to use? The one in CodeSourcery? > But how's assembler actually called? Just try to compile

my g++-cross was configured with following parameters: ./configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=armv7fl-montavista-linux-gnueabi --enable-cross --with-sysroot=/home/arm_v7_vfp_le/target/ --with-build-sysroot=/home/arm_v7_vfp_le/target/ --enable-shared --enable-languages=c,c++ --with-as=/home/arm_v7_vfp_le/bin/arm_v7_vfp_le-as

In ARM.td, I see that the ProcessorModel for cortex-r4, cortex-r4f, and cortex-r5 (as well as r7 and r8) is based on "CortexA8Model", which seems incorrect. When this was added in 2015, there were also comments associated with this configuration, such as "// FIXME: R5 has currently the same ProcessorModel as A8" (later removed). The processor model for Cortex-r52 appears to

I wrote: > In a floating point build > it's enabled only at complexity setting 10 Sorry. I meant that in a _fixed_point_ build the new analysis code is enabled only at complexity setting 10. It's currently enabled for floating point builds at complexity 7 or higher. Both fixed and float builds default to complexity 9 in 1.1. -r

Hi, Any help would b appreicated. This is one of my critical assignment. Thanks Sanjeev On Thu, Jun 17, 2010 at 7:03 PM, Sanjeev chugh <sanjuchugh at gmail.com> wrote: > Hello, > > Thanks for the reply. We have an product whose one part has lot of > algorithms doing some graphics work. Our intention was to figure out if > there can be any performance gain if we use llvm