similar to: encoding time

Hi, I would like to compile the Speex fixed-point, WB decoder for an AT91SAM7S256 ARM7 microcontroller using gcc-arm-elf and was wondering, before I roll up my sleeves and try to figure out all the autoconf things that I'm really unfamiliar with, if anyone else has done this and can share their experiences. I see in the archives that some folk have compiled for this processor before but

Good afternoon! Thank you for your product Speex. We want to use it in microcontroller AT91SAM7S256 (48 MHz). We applied the following: #define FIXED_POINT #define DISABLE_WIDEBAND #define DISABLE_HIGHPASS #define MANUAL_ALLOC #define OS_SUPPORT_CUSTOM at speex_encoder_init(&speex_nb_mode); speex_decoder_init(&speex_nb_mode); tmp=2; speex_encoder_ctl(st, SPEEX_SET_QUALITY,

ACE issued following PR: http://www.ace.nl/news/aces-cosy-compiler-framework-outperforms-llvm-arm9-processor Weird that they don't give any number and use ARM 9, do they mean cortex-a9 ?

Hello, I would like to run nut 2.6.1 on an embeeded machine ( arm9 ) running linux and uclibc. A working gcc tool chain came with the board. How can I compile and build nut using the cross compiler tool chain ? I know that this is not a very specific question. I have however little experience with cross compiling, and I wonder where to start. A logical point would be the configure script. It

Hi, I have read the decoding side performance on ARM7 or ARM9. Your comment is very useful for us on evaluating the possible usage of Speex on our ARM system. How about the encoding performance? In your article, you mentioned "optimization". What is it? Is it included the 1.1.6 release source codes? thanks, Jay -------------- next part -------------- An HTML attachment was

Hi, I have one question: Will Speex run in realtime (both encode / decode probably simulateusly) on Nokia 6600 --- basicaly ARM9 104MHz with Symbian 7s after porting to its C++ or Java? I am thinking mostly about the worst quality encoding (optionally duplex). Can this processor make it? Oh 6600 has something about 6mb memory if I remember good. Plase cc kangur@polcom.net in replies.

Good day, I have looked around for this information, but I have not been able to gain a clear understanding: what is the status of the LLVM ARM backend? That is, do the following work: 1. Generating Thumb code: I saw a video online where they describe an issue with using the ARM Thumb back-end 2. Generating code for ARM9 (ARMv5?) or ARM7 (ARMv4): again, the same presentation

Hi Tom Thanks, just at the feasibility phase right now, so this sort of info is really useful. Memory/MHz values for the Tremor/Vorbis code seem to vary wildly - at least I could not find a consistent set of numbers after trawling through the discussion groups... Thanks John -----Original Message----- From: tom abcd [mailto:tom.abcd@gmail.com] Sent: 28 March 2006 16:34 To: Anderton, John

Stripping out usused stuff is very easy, especially with static libraries. The only thing that could cause problem is the speed of the CPU. It's very hard to say what the requirements are because it depends a lot on the exact CPU you're using and (for ARM) the configuration of the cache and the speed of the bus. Jean-Marc Dennis Greenwood a ?crit : > Hi, > > I would like to

Evan, > I'm the code owner of LLVM codegen and targets. I'm also the one of main developers on the original ARM target. That means, I would make the decisions on major development on ARM target if there are decisions to be made. > > But my role is very different from what people are looking for in this thread. To properly qualify a target like ARM which are supported on many

I haven't tried using -Os/z on any ARM device for the last 3 years, and back then, -Os would break many things. People normally care about code size on Cortex-R/M and ARM9 or older, and in there, not many LLVM users. --renato On 27 February 2013 00:38, Jim Grosbach <grosbach at apple.com> wrote: > I've not run any on non-iOS devices, and haven't looked at GCC since >

Hello all, I'm a hardware person who has recently found himself thrust into a software role. So, please forgive any ignorance in the following questions. I've tried to do my homework reading the relevant manual pages and investigating the Doxygen documentation. :-) We're investigating acoustic echo cancellation solutions for a speech application. Our hardware will be a TI C64x+

I was trying to using llvm to targeting ARMv5TE -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180314/b9dadc37/attachment.html>

I have a question regarding ARM support. It was mentioned in mails below that LLVM supports ARM v6 but a lot of ARM v6 instructions are actually missing from ARM ISA description files( e.g. Media Instructions). Is there any documentation mentioning the unsupported parts of v6 version Thanks --Kapil On Thu, Sep 18, 2008 at 2:14 PM, Evan Cheng <evan.cheng at apple.com> wrote: > > On

Hi all I'm looking in to using speex for an ARM7 based speech decode development (note we need the decode only). My hope is that we should be able to run the decoder (in wideband mode) real time on the ARM7 (40MHz) without any problems (the difficulty would be in the encode - but we plan to run that offline on a PC - so we should be OK). Can anyone confirm that this is the case please? Also

Hi All, Currently I am investigating how interesting OGG is for me. The most important requirements are: - Decoding on embedded hardware, ARM7 or ARM9. - Mixing multiple audio streams/files on embedded hardware First of all how difficult is it to decode OGG on an ARM7/9 processor? I read that OGG decoding needs floating point support? Secondly I would like to know how many MIPS are needed to

Hi, I just realized that clang produces Thumb-2 instruction in code even when older CPU type which doesn't suport Thumb-2 is specified. Here is output: # /opt/llvm/bin/clang -S -ccc-host-triple arm-unknown-freebsd -mcpu=arm926ej-s -mfloat-abi=soft -v -o rrx.S rrx.c clang version 3.0 (http://llvm.org/git/clang.git 98138cdfdee05c0afbab2b209ce8cfe4a52474e1) Target: arm-unknown-freebsd Thread

? There seems to be a memory violation when calling celt_mode_create(48000, 240). ? The function compute_pulse_cache() calls celt_alloc (the second one, bits=celt_alloc()) in order to allocate 343 byte, but it is using about 872 bytes at that location, which will be deleted by the following allocations. ? In this case the following encoder call crashes at first run. ? Sorry, my time is very

On 22 June 2011 11:49, Damjan Marion <damjan.marion at gmail.com> wrote: > # /opt/llvm/bin/clang -S -ccc-host-triple arm-unknown-freebsd -mcpu=arm926ej-s -mfloat-abi=soft -v -o rrx.S rrx.c Even though you specified cpu as arm9, it's probably generating generic ARM IR (use -emit-llvm -S and see), which defaults to ARM instructions. If you want thumb, use triple =

On Jul 27, 2012, at 9:36 AM, Sebastien DELDON-GNB wrote: > ACE issued following PR: > http://www.ace.nl/news/aces-cosy-compiler-framework-outperforms-llvm-arm9-processor > Weird that they don't give any number and use ARM 9, do they mean cortex-a9 ? It's impossible to say. This sort of marketing statement is impossible to refute, because there are no details. Who knows whether