similar to: vorbis SSE diff

Displaying 20 results from an estimated 2000 matches similar to: "vorbis SSE diff"

2004 Aug 06
2
Notes on 1.1.4 Windows. Testing of SSE Intrinics Code and others
Jean-Marc, Are you sure that you don't need to add just -msse to enable the intrinsics rather than a full fledged -march=pentium3? I did some playing around and I can get intrinsics code to compile with -march=i686 -msse on linux with that. Check out:
2008 Apr 03
0
configure patch to check for SSE
Hi, The attached patch changes the configure.ac logic as follows: It tests if the current compiler/cflags combination supports SSE, and if so enables _USE_SSE. This can be overridden by the '--enable-sse' and '--disable-sse' flags. Using '--enable-sse' will additionally add '-O3 -msse' to CFLAGS, just as it used to. I've tested this using the following
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
2006 Jun 04
1
Help with compilation of app_conference in x86_64
Any C gurus out there that can tell me if this code compiled ok to be used in x86_64 (Pentium Dual Core). It's for the app_conference application. Im using Centos 4.3 x86_64 kernel: 2.6.9-34.ELsmp libgcc-3.4.5-2 gcc-3.4.5-2 after the compilation part is the makefile ************begin compilation******************* [root@centos app_conference]# make clean rm -f *.so *.o app_conference.o
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
2003 Apr 10
1
regchrome causes segfault during Mozilla build
>Submitter-Id: current-users >Originator: Dr. Otacon >Organization: Skimask Ninjas >Confidential: no >Synopsis: regchrome causes segfault during Mozilla build >Severity: critical >Priority: high >Category: ports >Class: sw-bug >Release: FreeBSD 4.8-STABLE i386 >Environment: System: FreeBSD octo.sytes.net 4.8-STABLE FreeBSD 4.8-STABLE #4: Wed Apr 9 14:48:08 MDT
2008 Jun 02
0
OT - Intel IPP 5.3
Hello, For education purpose, I would like to add G729 support to an Asterisk 1.4.19.1 system. I've read this : http://www.readytechnology.co.uk/open/ipp-codecs-g729-g723.1/ but when downloading Intel IPP software, it appears that latest IPP version is 5.3. As installation instructions here ( http://www.readytechnology.co.uk/open/ipp-codecs-g729-g723.1/doc-svn8.txt) relates to Intel IPP
2006 Oct 04
2
Crash in cb_search.c, line 414
Jean-Marc Valin wrote: > That's quite strange. The only thing I can say is that the bug is most > likely *not* around line 414. It's probably some sort of memory > corruption somewhere else (quite possibly outside of Speex). Do you have > any more information? What CPU? What's the value of best_ntarget[j]? Is > SSE enabled? What's the allocation method
2004 Aug 06
0
libspeex/SSE Intrinsics with GCC 3.3.x
I'm aware of the problem, but I don't know how to get autoconf to handle that properly. If someone knows how to make that work with autoconf even with non-gcc compilers and with default CFLAGS, I'm interested. Jean-Marc Le jeu 01/04/2004 à 17:21, Michael T. Dean a écrit : > When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be > added to the CFLAGS in
2013 Sep 15
2
PATCH: x86-64 support and SSE intrinscis code
Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > The biggest of these tweaks weas to disable the intrinsics version > fero FLAC__CPU_IA32 because I couldn't get this to compile on > i386-linux (and we have the nasm versions). Still open to re-enabling > this if someone can get it to work. I know you're a skilled programmer, but... maybe you forgot to add -msse
2004 Aug 06
3
libspeex/SSE Intrinsics with GCC 3.3.x
Here is code to add to configure.in to do what you want. It preserves CFLAGS and uses that var to hold the sse enable flags. You can subset this under the exisiting AC_ARG for sse or just make it do it all the time. If you notice the i?86, that means any x86 platform target will have it enabled. You can change that i686, but keep in mind that some distros compile/target for i386 on the glibc
2005 Mar 01
0
memory usage
Alfred E. Heggestad wrote: >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
2004 Aug 06
0
libspeex/SSE Intrinsics with GCC 3.3.x
Actually, I prefer having the user explicitly specify --enable-sse because you might want to compile for other machines than what you have. Also, any idea what happens if the user already has CFLAGS=-O2 defined (and you add -O3)? Last thing, how do you check whether gcc accepts -msse? Jean-Marc Le ven 02/04/2004 à 00:40, Aron Rosenberg a écrit : > Here is code to add to configure.in
2013 Sep 16
0
PATCH: x86-64 support and SSE intrinscis code
lvqcl wrote: > Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > > > The biggest of these tweaks weas to disable the intrinsics version > > fero FLAC__CPU_IA32 because I couldn't get this to compile on > > i386-linux (and we have the nasm versions). Still open to re-enabling > > this if someone can get it to work. > > > I know you're a
2004 Aug 06
2
libspeex/SSE Intrinsics with GCC 3.3.x
On Fri, Apr 02, 2004 at 12:08:52AM -0500, Jean-Marc Valin wrote: > I'm aware of the problem, but I don't know how to get autoconf to handle > that properly. If someone knows how to make that work with autoconf even > with non-gcc compilers and with default CFLAGS, I'm interested. It's easy enough to test whether gcc will accept -msse and ifdef out the intrinsics code
2013 Sep 17
2
PATCH: x86-64 support and SSE intrinscis code
Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: >> -msse for SSE code, -msse2 for SSE2 code, -msse4.1 for SSE4.1 code > > Yes, that was it. Brain fart. These flags were not needed on x86_64. > > Erik But now all C code is compiled with -msse2 and it won't work on older CPUs. Isn't it better to compile only necessary files with this flag?
2004 Aug 06
2
[PATCH] Make SSE Run Time option.
> > 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 than x87). Note that > > unlike the previous version which had a kludge to work with order 8 > > (required for wideband), this version only works with order
2004 Aug 06
0
[PATCH] Make SSE Run Time option.
Can you do another release of the unstable branch that has everything merged in? The run-time flags for SSE / ASM and your new intrinsics. If you have all the sections written, we will happily test them on windows QA machines. Is there anything in particular that you are looking for in testing? Or just that it works? Aron Rosenberg SightSpeed <p>At 01:17 PM 1/18/2004 -0500, you wrote:
2015 Mar 09
2
[PATCH 1/1] ensure that stack is aligned for SSE functions if using mingw32
Unable to test on win32 at the moment, please give this a try. Feedback welcome. Avoids crashes due to unaligned ops when built with mingw. --- src/libFLAC/include/private/cpu.h | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/src/libFLAC/include/private/cpu.h b/src/libFLAC/include/private/cpu.h index 8927897..bd40012 100644 --- a/src/libFLAC/include/private/cpu.h +++
2004 Aug 06
2
Notes on 1.1.4 Windows. Testing of SSE Intrinics Code and others
Jean-Marc, Good catch on the debug mode. After compiling the same code in release mode it does appear to be using all the registers correctly. Give us a few days to integrate our run-time flags into 1.1.4 and I will let you know how are testing turns out. Aron Rosenberg SightSpeed At 08:54 PM 1/21/2004, you wrote: > > 1. Compile Error with regular mode (FIXED_POINT undefined)