Re: [fpc-devel] win32 debugging broken in fixes_2_2?

2007-07-11 Thread Florian Klaempfl
Sergei Gorelkin schrieb: Wednesday, July 11, 2007, 12:06:51 AM, Florian wrote: FK Vinzent Hoefler schrieb: On Tuesday 10 July 2007 09:58, Vinzent Hoefler wrote: On Tuesday 10 July 2007 12:40, Yury Sidorov wrote: Maybe other way to detect SSE support exists... CPUID? To be more precise,

Re: [fpc-devel] win32 debugging broken in fixes_2_2?

2007-07-11 Thread Micha Nelissen
Yury Sidorov wrote: 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

Re: [fpc-devel] win32 debugging broken in fixes_2_2?

2007-07-11 Thread Florian Klaempfl
Micha Nelissen schrieb: Yury Sidorov wrote: 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

Re: [fpc-devel] win32 debugging broken in fixes_2_2?

2007-07-11 Thread Martin Schreiber
On Wednesday 11 July 2007 08.39, Florian Klaempfl wrote: That's a point though I thought we could safe this extra check because I didn't expect that a lot of people are still using PII :) A PII with 256MB ram is my main development machine. Do you see why MSEide+MSEgui is so fast? ;-) From

Re: [fpc-devel] win32 debugging broken in fixes_2_2?

2007-07-11 Thread Florian Klaempfl
Vinzent Hoefler schrieb: On Wednesday 11 July 2007 06:39, Florian Klaempfl wrote: That's a point though I thought we could safe this extra check because I didn't expect that a lot of people are still using PII :) Well, if the OS supports SSE and thus no SIGILL is generated, what would be