Displaying 20 results from an estimated 400 matches similar to: "Speex for armv6"
2011 Aug 09
4
not building with --enable-arm-asm -enable-arm5e-asm
Hi,
I am getting the following dump while trying to build for arm
./configure --prefix=/root/dump --host=arm-linux --with-gnu-ld
--disable-static --enable-fixed-point --enable-arm-asm -enable-arm5e-asm
configure: WARNING: unrecognized options: --enable-arm-asm
Type "make; make install" to compile and install Speex
root at rony-ubuntu:~/speex# make
make all-recursive
make[1]:
2005 Mar 25
2
Port speex to my iPAQ 1945
Hi
I want to port speex to my pocket PC iPAQ1945 which has a Samsung
processor 2410, an ARM9-based processor. I would like to write the
specific optimized code for this chip. I had some experience at DSP
chip and fixed-point coding but know nothing about embedded system and
ARM. Could someone tell me some hint how to write optimized code for
this pocket PC. If you can give me some links that will
2011 Jun 17
1
speex on arm
Hi All,
I'm trying to build speex for the mini2440 board, with this toolchain: http://www.friendlyarm.net/dl.php?file=arm-linux-gcc-4.3.2.tgz
because speex is a dependency of the sip softphone 'linphone'.
The 'configure' string I'm using is this:
./configure --prefix=/usr --host=arm-linux --with-gnu-ld --disable-static --enable-fixed-point --enable-arm-asm
Other
2013 May 17
1
[Patch]01-Add ARM5E macros
Hello,
This is a first patch which add macros for ARMv5E.
Also, I copy headers from other files and add company name, tell me if
I'm wrong.
Also, if you have any question or comment about it, feel free to contact me.
Best regards,
--
Aur?lien Zanelli
Parrot SA
174, quai de Jemmapes
75010 Paris
France
-------------- next part --------------
diff --git a/celt/fixed_arm5e.h
2005 Mar 27
0
Port speex to my iPAQ 1945
Hi,
A question, How to embed inline assembly in EVC++? Can EVC link
with obj file generated by pocketgcc?
thanks
James
(sorry , last time I sent it to *.ca) On Sat, 26 Mar 2005 11:11:50
-0500, Jean-Marc Valin
<Jean-Marc.Valin@usherbrooke.ca> wrote:
> Hi,
>
> Assuming you have gcc, you can already compile with --enable-arm5e-asm
> and get good results. Right now, many
2004 Aug 06
2
Speex on Nokia 6600
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.
2004 Aug 06
1
Compile issue with gcc3.2
I've been able to get Speex to compile on gcc 2.95.3 with no problems. When using gcc 3.2 I get the following output:
gcc -DHAVE_DLFCN_H=1 -DHAVE_SYS_SOUNDCARD_H=1 -DHAVE_LIBOGG=1 -DHAVE_LIBM=1 -DVERSION=\"1.0beta1\" -I. -I. -march=pentium4 -mcpu=pentium4 -O3 -pipe -c high_lsp_tables.c -o high_lsp_tables.o
cb_search.c: In function `split_cb_search_shape_sign':
cb_search.c:500:
2007 Dec 12
2
Speex crashing on ARM with assembler optimization enabled.
Hi,
I'm trying to get speex working on an ARM board (ARM926EJ-Sid(wb) core,
ARM 5TE architecture) and getting segfaults if build with "--enable-fixed-point
--enable-arm5e-asm" options. If I use just "--enable-fixed-point", then
it runs fine, but once I add "--enable-arm5e-asm" it start crashing
(I use testenc to test it).
Further investigation showed, that it
2004 Aug 06
0
Speex on Nokia 6600
> 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.
I'm not sure the
2014 Sep 20
1
Building under MSVC & MinGW
I am attempting to build the RC1 drop of libspeex for Windows with the MSVC toolchain (VS2013) and MinGW, the following is my configure line:
CC=cl.exe CFLAGS=-MD ./configure --enable-shared=no --prefix /builds/Windows81/x86 --host i686-pc-mingw32
During the configure process (specifically the "checking whether the C compiler works...") I get a Windows popup telling me that the test
2005 Jan 25
1
"spx_word16_t *" is incompatible with parameter of type "float *"
Hi,
I am bring SPEEX up on Analog Device's Blackfin (using Visual DSP++ tool set). The floating point was too slow on this fixed-point processor so I am going for the integer version.
The floating point library build was very clean, but when I build with FIXED_POINT defined, the compiler exits when it find this discrepancy in \libspeex\cb_search.c :
".\libspeex\cb_search.c",
2004 Aug 06
3
Speex on Nokia 6600
Hmm, what these instructions do? (I know nothing about ARMs; I have some
knowlege about x86 assemblers and programming). Cant we use pure standard
C++ or Java? Does Speex work with fixedpoint math? (As far as I know Java
on 6600 has no builtin floatingpoint, there is emulation class somewhere
on the net, but it is probably painfully slow.) I do not know if this
processor has builtin
2014 Feb 08
3
[PATCH 1/2] arm: Use the UAL syntax for ldr<cc>h instructions
On Fri, 7 Feb 2014, Timothy B. Terriberry wrote:
> Martin Storsjo wrote:
>> This is required in order to build using the built-in assembler
>> in clang.
>
> These patches break the gcc build (with "Error: bad instruction").
Ah, right, sorry about that.
> Documentation I've seen is contradictory on which order ({cond}{size} or
> {size}{cond}) is correct.
2006 Sep 18
2
Exc CB Search very little Question
Hello,
just to make sure I haven't gotten anything wrong:
In cb_search.c (function split_cb_search_shape_sign) after all that
searching nb_subvect CB entries are being written into the stream. These
are all taken from the same codebook.
If I wanted to, I could just change their order, couldn't I?
Because important is only the linear combination of them all together,
which I keep
2014 Jun 20
2
Alleged bug in Silk codec
Yes those instructions exist, although they're a bit slower than the basic
16x16->32 with 32-bit accumulation (SMLABB). So I'd be surprised if the
function with 64 bit accumulation would run as fast as the current code.
Don't know how much we care about 16-bit platforms. And accuracy should
not matter.
On the other hand, a 64-bit implementation is much cleaner/shorter, which
is
2014 Feb 08
0
[PATCH v2] arm: Use the UAL syntax for instructions
This is required in order to build using the built-in assembler
in clang.
---
I squashed the two changes since it would break the normal gcc
build otherwise.
---
celt/arm/arm2gnu.pl | 2 ++
celt/arm/celt_pitch_xcorr_arm.s | 18 +++++++++---------
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/celt/arm/arm2gnu.pl b/celt/arm/arm2gnu.pl
index eab42ef..5c24758 100755
---
2005 May 10
2
Encoder performance on ARM9
Hi Jean-Marc,
>I think it's worth trying the float version on your CPU. However, I
>wouldn't be surprised if the fixed-point was still faster than float.
ok, I'll try both configurations.
>BTW, you can use --enable-arm5-asm instead of --enable-arm4-asm. While
>both are currently almost the same, eventually it would be possible to
>get better performance using the
2014 Feb 07
3
[PATCH 1/2] arm: Use the UAL syntax for ldr<cc>h instructions
This is required in order to build using the built-in assembler
in clang.
---
celt/arm/celt_pitch_xcorr_arm.s | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/celt/arm/celt_pitch_xcorr_arm.s b/celt/arm/celt_pitch_xcorr_arm.s
index 09917b1..3c4b950 100644
--- a/celt/arm/celt_pitch_xcorr_arm.s
+++ b/celt/arm/celt_pitch_xcorr_arm.s
@@ -309,7 +309,7 @@
2006 Jan 23
2
Compiler warnings with GCC 3.4.4 and perfomance question on a Arm 7
I am using speex on a Philips LPC2138 Arm 7 processor and have hit two
compiler warnings when using FIXED_POINT and the Arm 4 asm code.
In cb_search.c get a warning on the call to compute_weighted_codebook of:
"passing arg 2 of 'compute_weighted_codebook' from incompatible pointer type'
In cp_search_arm4.h it is defined as:
static void compute_weighted_codebook(const signed
2011 Jun 18
0
[LLVMdev] RFC: Integer saturation intrinsics
> The plan is to form calls to these intrinsics in InstCombine. Legalizer
> can expand these intrinsics if they are not legal. The expansion should
> be fairly straight forward and produce code that is at least as good as
> what LLVM is currently generating for these code sequence.
SSAT/USAT may set the Q (saturation) flag, which might cause problems
for anyone relying on explicitly