similar to: [LLVMdev] Config LLVM with --enable-targets=arm , how to make Clang generate code for ARM Cortex-A8?

hi all I saw that llvm-2.7 support arm cortex-a8 now, but I didn't find how to cross build it. thank you all -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100505/976c140e/attachment.html>

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

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

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

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.

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

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

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:

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

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

Looks OK to me, but I don't have any Cortex-M3 docs to confirm the choice of v7-A without NEON. deep On Sun, Nov 22, 2009 at 9:47 PM, Bagel <bagel99 at gmail.com> wrote: > Here is a one-line patch to support the cortex-m3. > For those who plan the features for ARM, the new cortex-m0 implements only a > subset of the Thumb2 instructions.  I still have yet to see a document that

On 27 November 2013 14:55, Richard Pennington <rich at pennware.com> wrote: > Your link says that clang is using gcc to compile rather than compiling > directly. You might want to look at the ELLCC project, which is designed for > just the sort of cross compilation you are trying to do. http://ellcc.org Hi Rich, No, his output only has gcc to assemble and link:

On 11/27/2013 07:57 AM, Rob Stewart wrote: > On 26 November 2013 16:44, Renato Golin <renato.golin at linaro.org> wrote: >> 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, > I'm honoured. (But Rob is also OK)

> cortex-a8 vfpv4 with ffp-contract=fast : vfma instruction emitted ( this > seems a bug to me!! If cortex-a8 doesn't come with vfpv4 then vfma > instructions generated will be invalid ) If I'm understanding correctly, you've specifically told it this Cortex-A8 *does* come with vfpv4. Those kinds of odd combinations can be useful sometimes (if only for tests), so I'm not

I have tracked it down to the real reason. The revisions 139934-139937 has changed the order in which configure chooses a compiler. Clang is checked first, then llvm-gcc, and then gcc. I can see the reason for this change. However, in this particular case it has broken the build because Ubuntu includes clang 2.8 which doesn't know where includes are. I have removed clang from the host to