Displaying 4 results from an estimated 4 matches for "361x".
Did you mean:
361
2005 Feb 28
4
memory usage
On Mon, 2005-02-28 at 19:42 -0500, Jean-Marc Valin wrote:
> > jean-marc: i think we can remove spx_sig_t *orig.
> > but am not sure about exc2Buf. is it for extension?
>
> orig is already removed in SVN (which you should probably use). As for
> exc2, it can be removed, but I'm not sure if you can just use exc
> instead (maybe yes).
>
when removing "spx_sig_t
2005 Mar 01
0
memory usage
...I did a bunch of tests of encoder performance (on an Athlon XP 1700+) a
while back, and found that, for 8kbps CBR complexity 1, I got:
(encode/decode speed)
basic compile: 29.2x / 168x
-O3 -ffast-math -funroll-all-loops
-march=pentium3 -fprefetch-loop-arrays -fsingle-precision-constant:
53.4x / 361x
With -msse: 65x/386x
The actual numbers don't matter much, but it does mean that encoding is
almost 6x as expensive as decoding, so expect that you're going to use
60-90% of your CPU for speex encode..
-SteveK
-------------- next part --------------
An HTML attachment was scrubbed....
2004 Aug 06
1
libspeex/SSE Intrinsics with GCC 3.3.x
On Fri, Apr 02, 2004 at 12:33:13AM -0500, Jean-Marc Valin wrote:
> Do you have any sample code for that? Also, how do you tell autoconf to
> append '-msse' without running into problems when CFLAGS is not set (and
> usually defaults to -g -O2, but not always).
Example patch attached. It only tries if the use passes --enable-sse;
testing by target arch as Aron suggested is
2004 Aug 06
4
libspeex/SSE Intrinsics with GCC 3.3.x
When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be
added to the CFLAGS in libspeex/Makefile.
GCC 3.1.1 added a new option "-msse" (see
http://gcc.gnu.org/gcc-3.1/changes.html , specifically under "New
Targets and Target Specific Improvements") to enable SSE instructions
within the compiler's output (for appropriate architectures).
Compiling speex on