Displaying 20 results from an estimated 400 matches similar to: "gcc-4.1: svn 10958 fix point build fails"
2006 Mar 01
0
gcc-4.1: svn 10958 fix point build fails
I'm not sure what you're trying to achieve here, but SSE and fixed-point
are mutually exclusive.
Jean-Marc
On Sat, 2006-02-25 at 19:02 -0500, sean darcy wrote:
> Building svn 10958 on amd64, gcc-4.1:
>
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I..
> -I/usr/include -O2 -fPIC -funswitch-loops -fvisibility-inlines-hidden
> -march=k8 -ftree-vectorize
2006 May 25
1
how to study the speex source code
I am studying the speex 1.0.5 C source code ,but i feel it is hard
to understand the code ,especially the ltp.c and filters.c file.
may you tell me the detail algorithm or the more detail notation of the
source code of this two file.including below functions
void open_loop_nbest_pitch(float *sw, int start, int end, int len, int
*pitch, float *gain, int N, char *stack);
float
2004 Aug 06
3
[PATCH] Make SSE Run Time option.
Le jeu 15/01/2004 à 15:30, Daniel Vogel a écrit :
> Unrelated, but please use SSE/MMX/... intrinsics on Windows instead of using
> inline assembly so you also get the speed benefit on Win64.
OK, so here's a first start. I've translated to intrinsics the asm I
sent 1-2 days ago. The result is about 5% slower than the pure asm
approach, so it's not too bad (SSE asm is 2x faster
2004 Aug 06
0
[PATCH] Make SSE Run Time option. Add Win32 SSE code
> There is a big difference between SSE and SSEFP. The SSEFP means
> that the CPU supports the xmm registers. All Intel chips with SSE support
> do, however no current 32 bit AMD chips support the XMM registers. They
> will support the SSE instructions but not those registers. You are right
> about the SSE2 not being used.
I'm still not sure I get it. On an Athlon
2006 Jan 18
2
TI 6xxx platform performance
I'm trying to make a design decision between a TI 6416 or DM642 (fixed
point) and 6713 (floating point) platform. The application is a 32 channel
speech encoder. (CBR only, 8khz, 8kbps)
To get a feel for the computational load, I am running 1 second (50 frames)
of voice through the encoder.
My profile of the 6416 indicates I'm at 27.4M cycles/channel. I need to get
below 720Mhz/32
2004 Aug 06
2
[PATCH] Make SSE Run Time option. Add Win32 SSE code
Jean-Marc,
There is a big difference between SSE and SSEFP. The SSEFP means
that the CPU supports the xmm registers. All Intel chips with SSE support
do, however no current 32 bit AMD chips support the XMM registers. They
will support the SSE instructions but not those registers. You are right
about the SSE2 not being used.
The AMD Opterons are the first AMD CPU's which support
2005 Apr 20
2
Speex-1.1.7 seems to crash with --enable-sse (on P3/GCC-3.2)..
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<b></b>Hi,<br>
<br>
I also tried to build speex
2006 Jan 18
2
Errors in speex lib with Blackfin
Hello!
I'v downloaded speex lib 1.1.11.1.
I am trying to port speex lib to Blackfin processor.
I am using VisualDSP++ 4.0.
If I am compiling source codes with using floating point everything
ok.
When I am compiling with FIXED_POINT defined everything's ok and code
works about two times faster.
But when I am defining BFIN_ASM I am getting several compiling errors
in Blackfin assembler
2005 Mar 08
1
Speex-1.1.7 seems to crash with --enable-sse (on P3/GCC-3.2)..
I tried building speex with SSE, and found that it crashes for me here:
[This is on RH=8.0]:
# libtool gdb ./src/speexenc
GNU gdb Red Hat Linux (5.2.1-4)
[...]
This GDB was configured as "i386-redhat-linux"...
(gdb) r --rate 8000 --16bit -n /dev/zero /tmp/foo
Starting program: /usr/src/speex-1.1.7/src/.libs/lt-speexenc --rate 8000
--16bit -n /dev/zero /tmp/foo
Encoding 8000 Hz audio
2004 Aug 06
2
SmartPhone ARM
>What frequency is the ARM processor?
The phone shows ARM720 no freq.
I'm going to have to guess around 100 Mhz.
I ran the same code on an XSCALE ARM 400 mhz. Toshiba e740.
Runs about .33 -> .4x realtime. This is the using the generic fixed point
defines.
Around 5 times faster than I am seeing with the Orange SPV e100.
I am using the 1.1.3 codebase.
Thanks for taking the time to
2004 Aug 06
1
Real time audio encoding - cpu usage
Hello Jean-Marc
>If you want to do it, I can show you
>what functions (there are 2-3) to port. Otherwise I might do it
>eventually, but it's not a top priority (there's already an SSE version
>though).
I would indeed like to know which functions can be used to improve K6-2
performance through 3DNow.
Cheers
Bjoern D. Rasmussen
<p><p><p>>From: Jean-Marc
2004 Aug 06
2
Coredumps when --enable-sse is selected
System: Linux 2.4.25, glibc-2.3.2, gcc-3.2.3 (weird palindrome there), on a
Williamette core Pentium 4 (1.6Ghz) system.
I've tried both speex 1.1.5 release, and the current CVS (which self-IDs as
1.1.4), and the result is the same.
I suspect some funk in the use of the SSE intrinsics macros.
Backtrace:
#0 0x40024594 in filter_mem2_10 (x=0x805f31c, _num=0x8061fb8,
_den=0x8061fe4,
2004 Aug 06
2
[PATCH] Make SSE Run Time option. Add Win32 SSE code
All,
Attached is a patch that does two things. First it makes the use
of the current SSE code a run time option through the use
of speex_decoder_ctl() and speex_encoder_ctl
It does this twofold. First there is a modification to the configure.in
script which introduces a check based upon platform. It will compile in the
sse assembly if you are on an i?86 based platform by making a
2004 Aug 06
4
Speex test cases?
I'm trying to get speex to encode a bit faster, mainly by rewriting a few
functions in SSE and translating the GCC __asm__ to VC __asm.
There's 2 functions I'm targeting, first is vq_nbest which consumes 40% of
the time at high complexity and split_cb_search_shape_sign. Which consumes
just over 30%. I've split out two functions from:
cb_search_precompute_energy - loop at the
2005 Apr 20
0
Speex-1.1.7 seems to crash with --enable-sse (on P3/GCC-3.2)..
Hi,
To increase the stack size, you can increase the value in the
speex_alloc() call in nb_celp.c. Let me know if it solves the problem.
Also, what compiler are you using. I think some older versions of gcc
may have problems with SSE intrinsics.
Jean-Marc
Le mardi 19 avril 2005 ? 16:02 +0200, jehan Monnier a ?crit :
> Hi,
>
> I also tried to build speex 1.1.7 with sse enabled on a
2008 Aug 02
1
fir_mem16,iir_mem16 and filter_mem16 optimisations
-----Original Message-----
From: Jean-Marc Valin <jean-marc.valin at usherbrooke.ca>
To: ??????? ??????? <altersoft at mail.ru>
Date: Sat, 02 Aug 2008 07:54:34 -0400
Subject: Re: [Speex-dev] fir_mem16,iir_mem16 and filter_mem16 optimisations
>
> ??????? ??????? a ?crit :
> > I have some questions about that functions: fir_mem16, iir_mem16 and filter_mem16.
> >
2006 Jan 05
2
Re: sigsegv in _mm_load_ups (linux/gcc 3.x)
That's definitely strange and I've never encountered that. Normally, the
only way for _mm_load_ups to generate a segfault is for the input to be
invalid memory, in which case the C version should crash too. I suspect
the compiler (or something else) may be hiding the real problem. Can you
get a debugger and see exactly what assembly statement is causing the
crash and what the operands are?
2005 May 25
3
Speex on TI C6x, Problem with TI C5x Patch
Hi Jean-Marc, Hi Jim,
I have also seen some problems with the 1.1.8 release on the C55x. So far I
have boiled down the issues to the following:
1) We need our own "fixed_xx.h" header file. I don't know why, and haven't
had time to investigate, but there is a definite improvement when I use the
attached fixed_c55x.h file which has turned all the maths into inline
functions.
2004 Aug 06
0
Coredumps when --enable-sse is selected
Hi,
I've tried the same configure options on my system and it doesn't crash.
I have the same glibc and gcc 3.3.2 (can you see if a newer gcc works?).
Also, could you explore a bit with different options so we can narrow it
down a bit. For example, does it work with the default CFLAGS or without
--vbr or --dtx. Last thing, maybe it's the file. If so, please send me
the smallest sample
2005 Dec 06
1
ARM4 filter code
I have found that filter_mem2 fixed point does not match the inlined
assembly version for arm4. Looking closer there appears to be an off by
one error. It occurs when setting the value of mem at the end of the
inner loop. In the C fixed point version this is done with a subtract.
In the arm4 version instead of multiplying den by yi, it is multipled by
nyi and then an add is done. This