Displaying 9 results from an estimated 9 matches for "v5te".
Did you mean:
v5t
2006 Oct 20
1
Speex for XScale IXP425
Hi,
I was wondering if anyone had managed to get speex to run (nicely) on
an IXP425 processor. The current version does not seem to have the
necessary optimisations for the ARM v5te, just the v5 which has
assembly optimisations not understood by this target.
Failing that, does anyone know where I might get a reference for this
model of processor? I have look on the Intel site, but I can't seem to
find one there.
Thanks,
lee
--
2016 Jan 08
2
Diff to add ARMv6L to Target parser
...: lib/Support/TargetParser.cpp
===================================================================
--- lib/Support/TargetParser.cpp (revision 257090)
+++ lib/Support/TargetParser.cpp (working copy)
@@ -401,6 +401,7 @@
.Case("v5", "v5t")
.Case("v5e", "v5te")
.Case("v6j", "v6")
+ .Case("v6l", "v6")
.Case("v6hl", "v6k")
.Cases("v6m", "v6sm", "v6s-m", "v6-m")
.Cases("v6z", "v6zk", "v6kz")...
2010 May 08
1
[LLVMdev] Question about maturity of various ARM instruction sets in llvm 2.6
Thanks in advance,
Are all of the ARM instruction sets that can be specified with -mattr stable? I'm specifically interested in -mattr=+v5te. I'm attempting to build a cross-compiling llvm-gcc to build for Android. The Android native toolchain builds for ARMv5te.
--Robb
2005 Oct 18
0
performance speex on ARM
Well,
all ARM9E cores use the v5TE architecture, which means Thumb
and DSP-friendly instructions.
Ettore Benedetti
THALES COMMUNICATIONS B.V.
Bestevaer 46, 1271 ZA Huizen
The Netherlands
Unclassified
>>> tk <tunkeat@gmail.com> 10/15/05 7:15:20 AM >>>
hi,
i have searched through the archives but did no...
2012 Jul 22
3
[LLVMdev] Setting up a cross-compiler for cortex-m3
...; 0x30
> ...
>
> I'm not 100% sure if that's the correct ISA, because I haven't run the
> code, but it seems ok.
>
Unfortunately, I have to resurrect this thread.
I had the time to test the code, and it is using the wrong ISA.
I can't understand why, but it uses armv5te instead of thumb2.
$ clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple
thumbv7m-none-gnueabi testReference.cpp -c
$ arm-none-linux-gnueabi-readelf -A testReference.o
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "5TE"
Tag_CPU_arch: v5TE
Tag_ARM_ISA_use: Yes...
2014 Jul 09
5
[LLVMdev] [PATCH][REQUEST] Could someone submit this CSR Kalimba definitions patch please?
...sion
+ kalimba // Kalimba: generic kalimba
};
- enum SubArchType {
- NoSubArch,
-
- ARMSubArch_v8,
- ARMSubArch_v7,
- ARMSubArch_v7em,
- ARMSubArch_v7m,
- ARMSubArch_v7s,
- ARMSubArch_v6,
- ARMSubArch_v6m,
- ARMSubArch_v6t2,
- ARMSubArch_v5,
- ARMSubArch_v5te,
- ARMSubArch_v4t,
- ARMSubArch_v4
- };
enum VendorType {
UnknownVendor,
@@ -104,7 +89,8 @@
BGQ,
Freescale,
IBM,
- NVIDIA
+ NVIDIA,
+ CSR
};
enum OSType {
UnknownOS,
@@ -164,9 +150,6 @@
/// The parsed arch type.
ArchType Arch;
- /...
2012 Jul 18
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Wed, Jul 18, 2012 at 5:45 PM, Renato Golin <rengolin at systemcall.org> wrote:
> On 18 July 2012 15:46, salvatore benedetto
> <salvatore.benedetto at gmail.com> wrote:
>> $ clang++ -ccc-host-triple thumbv7m-none-gnueabi noInclude.cpp -c
>> --sysroot=/home/emitrax/CodeSourcery/Sourcery_G++_Lite/arm-none-linux-gnueabi/libc/
>
> Try -ccc-gcc-name
2012 Jul 18
3
[LLVMdev] Setting up a cross-compiler for cortex-m3
On 18 July 2012 15:46, salvatore benedetto
<salvatore.benedetto at gmail.com> wrote:
> $ clang++ -ccc-host-triple thumbv7m-none-gnueabi noInclude.cpp -c
> --sysroot=/home/emitrax/CodeSourcery/Sourcery_G++_Lite/arm-none-linux-gnueabi/libc/
Try -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple
thumbv7m-none-linux-gnueabi
Sometimes it's better than sysroot, as it finds it
2016 Jan 05
6
Diff to add ARMv6L to Target parser
> You assume triples make sense. That's the first mistake everyone does
> when thinking about triples. :)
I know they don't make sense in many corner cases, but I think
discarding logic where it *does* exist is a mistake.
> AFAIK, "ARMv7B" is only used by HighBank, which is no more. But that,
> too, was "ARMv7A big endian".
I believe it's what any