Displaying 20 results from an estimated 120 matches similar to: "Coredumps when --enable-sse is selected"
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
2004 Aug 06
1
speex and thread question.
Hy,
I'm writing a application using speex.
This app have two threads one is encoding the other one decoding using
speex.
I dont know why but I got segfault on some systems.
If I juste take off one of the thread like encoding and lauchin the
decoding part in a thread and the application is still segfaulting.
But if I just launch the decoding process with out a thread every thing
is going
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
5
[PATCH] Make SSE Run Time option.
> Personally, I don't think much of PNI. The complex arithmetic stuff they
> added sets you up for a lot of permute overhead that is inefficient --
> especially on a processor that is already weak on permute. In my opinion,
Actually, the new instructions make it possible to do complex multiplies
without the need to permute and separate the add and subtract. The
really useful
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
2002 Aug 05
1
WMT?
Hi,
The VP3 source code supports various CPU-specific optimized
instructions. I see references to MMX and XMM (SSE2). I also see
references to WMT. What is WMT?
Thanks...
--
-Mike Melanson
<p><p>--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
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?
2003 Jun 16
2
[Bug 596] "ProxyCommand none" doesn't work
http://bugzilla.mindrot.org/show_bug.cgi?id=596
Summary: "ProxyCommand none" doesn't work
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: openssh-bugs at mindrot.org
ReportedBy:
2004 Aug 06
2
[PATCH] Make SSE Run Time option. Add Win32 SSE code
Jean-Marc,
>I'm still not sure I get it. On an Athlon XP, I can do something like
>"mulps xmm0, xmm1", which means that the xmm registers are indeed
>supported. Besides, without the xmm registers, you can't use much of
>SSE.
In the Atholon XP 2400+ that we have in our QA lab (Win2000 ) if you run
that code it generates an Illegal Instruction Error. In addition,
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
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
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
2009 Jan 03
8
OpenGl or Coredumps problems???
Good Afternoon!!! I am using a wine 1.1.12 version and after a source code install I don't get run applications. In konsole I had "wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart" during games running. But Driver Paralel game has a tester and it's showing 3d problems.
I'm using a slack 12.1 and nvidia 7300 gt. Can someone help me???
2005 Sep 05
0
1.0a1 Coredumps / errors when moving multiple
I've just tried upgrading 1.0t51 to 1.0a1 and it has been........ difficult.
I've been getting logs of Sig11s and other errors, and have trouble
tracking them down.
Main problem seems to be with moving / copying messages. One at a time
works (mostly), multiple will coredump the imap process (not yet managed
to get a proper core out though...)
I'm using imap & Maildir,
2010 Jan 04
1
bin/exec/R coredumps (PR#14177)
Full_Name: Jens Elkner
Version: 2.10.1
OS: Solaris
Submission from: (NULL) (87.188.113.172)
elkner.idev2 elkner/build/R-2.10.1 > bin/exec/R -e
Segmentation fault (core dumped)
elkner.idev2 elkner/build/R-2.10.1 > dbx bin/exec/R core
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.7' in your
.dbxrc
Reading R
core
2004 Aug 06
2
Coredumps when --enable-sse is selected
> 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?).
When I build it with gcc-3.3.3, the problem disappears. I guess the older
gcc's XMM macros were buggy.
Thanks for the suggestion.
> Also, could you explore a bit with different options so we can narrow it
> down a bit.
2003 Sep 12
2
Possible new configure option: --with-fatal-coredumps?
Hi all.
What's the feeling about adding a new configure-time option to generate a
core dump on when fatal() is called?
It might help debug certain types of problems, but runs the risk of
sensitive information being left in the core dump. Obviously, it should
default to "no".
Anyone like the idea? Anyone hate it?
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 /
2008 Mar 29
0
GCC/ELF Visibility patch
Hi,
I've attached a patch against SVN r14645 which adds GCC visibility
information to all symbols exported from libspeex.so and libspeexdsp.so.
It includes a configure.ac change to test that both the compiler flags and
__attribute__((visibility)) works, and if so will
#define EXPORT __attribute__((visibility("default")))
and if not
#define EXPORT
I've attached a diff output
2010 Jul 31
2
[PATCH] Enable coredumps to be captured from the appliance (RHBZ#619334).
https://bugzilla.redhat.com/show_bug.cgi?id=619334
This is a slightly unsatisfactory patch which allows coredumps to be
captured when they occur inside the appliance. You can capture
coredumps by doing:
export LIBGUESTFS_COREDUMP=/sysroot/core.%t.%p.%e
or equivalently:
g.set_coredump ("/sysroot/core.%t.%p.%e")
or variations thereof, see the manual page.
When a coredump occurs,