On Sad, 2004-09-25 at 04:41, Patrick McFarland wrote:
Not to sound ignorant, but isn't that a bug in the
mobo/bios/chipset/processors? That shouldn't even be possible, should
it? (And if it 'is', shouldn't Linux disable SSE usage on both
processors?)
You can mix PII and PIII processors in a
On Thu, 23 Sep 2004 16:50:26 +0100, Alan Cox [EMAIL PROTECTED] wrote:
Should do. There is a corner case of SMP with only one CPU having SSE
but thats already broken in Mesa and many other packages.
Not to sound ignorant, but isn't that a bug in the
mobo/bios/chipset/processors? That shouldn't
At the time the code was written (fall 1999?) the only way Gareth found
that he could reliably determine that SSE was fully supported (by CPU
and kernel) was to try executing an SSE instruction and catching the
exception if it failed.
If there's a better way of doing that nowadays, we could
Philipp Klaus Krause wrote:
Does that mean that software Mesa doesn't use SSE?
The problem occurs only with the r200 driver, not with software
rendering.
Okay, then the SSE test can't be the problem. The exact same code gets
executed in both the R200 driver and software Mesa. Actually, do you
On Mer, 2004-09-22 at 22:14, Eric Anholt wrote:
2.2 kernels and kernels not properly configured for Pentium3 CPUs. So,
what's the right way on a 2.4 or a 2.6 kernel to determine if an app can
use SSE? What about BSD?
On FreeBSD we just use a convenient little sysctl to pull out
Ian Romanick schrieb:
Philipp Klaus Krause wrote:
Does that mean that software Mesa doesn't use SSE?
The problem occurs only with the r200 driver, not with software
rendering.
Okay, then the SSE test can't be the problem. The exact same code gets
executed in both the R200 driver and software
Alan Cox wrote:
On Mer, 2004-09-22 at 22:14, Eric Anholt wrote:
2.2 kernels and kernels not properly configured for Pentium3 CPUs. So,
what's the right way on a 2.4 or a 2.6 kernel to determine if an app can
use SSE? What about BSD?
On FreeBSD we just use a convenient little sysctl to pull out
On Iau, 2004-09-23 at 17:22, Ian Romanick wrote:
The folks on #freedesktop suggested parsing cpuinfo, and I wrote some
simple code to do that. Are you saying that, if CPUID returns the SSE
bit set and we're on a 2.4 or later kernel, we're good to go? That
would make me very happy because
Alan Cox wrote:
Should do. There is a corner case of SMP with only one CPU having SSE
but thats already broken in Mesa and many other packages. The more
thorough case is you use /dev/cpu/%d/cpuid to check the CPUid on each
processor but I'm not sure thats neccessary in reality
I had that issue in
On Iau, 2004-09-23 at 17:21, Philipp Klaus Krause wrote:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x4D4E5A16
Function=(null)+0x4D4E5A16
Looks like a buffer overrun or memory corruption. Are you trying to
use mesa very
On Wed, 2004-09-22 at 13:21, Ian Romanick wrote:
Philipp Klaus Krause wrote:
_mesa_test_os_sse_exception, executed upon start of any OpenGL
application raises SIGFPE. Normally this is not a problem,
applications continue to execute normally.
However when using the jogl OpenGL Java
_mesa_test_os_sse_exception, executed upon start of any OpenGL
application raises SIGFPE. Normally this is not a problem,
applications continue to execute normally.
However when using the jogl OpenGL Java binding programs exit.
I tried both with Java 1.4 from Sun and sablevm.
Philipp
12 matches
Mail list logo
