From: "Florian Klaempfl" <[EMAIL PROTECTED]>
Martin Schreiber schrieb:
On Tuesday 10 July 2007 14.53, [EMAIL PROTECTED] wrote:
And what should I do in MSEide? Disable SIGILL reporting by gdb?
How does Lazarus handle the problem?
It does not handle it. If you handle it in MSEIDE, please let us
know how
you did it.
The IDE must check where the SIGILL is created, prevent error
reporting and
restart the program if the SIGILL is raised in the FPC SSE checking
code...
Question to the FPC developers:
Is there really no other method to check for SSE support?
No, silly enough. Checking some cpuid result is enough to check if
the
CPU supports it. But CPU support doesn't mean OS support. And to
check
if the OS supports SSE you've to execute an sse instruction and
handle
the exception.
Florian, to prevent SIGILL on non SSE CPUs we can first check CPUID
and execute sse instruction only if CPUID reports SSE support.
Yury.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
