HEADS UP: SSE instructions (Re: cvs commit: src/share/mk bsd.cpu.mk)

2002-09-06 Thread Kris Kennaway
On Fri, Sep 06, 2002 at 06:15:29PM -0700, Maxime Henrion wrote: mux 2002/09/06 18:15:29 PDT Modified files: share/mk bsd.cpu.mk Log: Update to use all the new CPU optimizations of GCC3. Reviewed by:kris Note that you'll need to have 'options

Re: HEADS UP: SSE instructions (Re: cvs commit: src/share/mk bsd.cpu.mk)

2002-09-06 Thread Kris Kennaway
On Fri, Sep 06, 2002 at 09:28:28PM -0400, Kenneth Culver wrote: Athlon XP processors support SSE instructions, but not at the same time as 3dnow instructions. The processor has to switch modes or something like that. What if a user wants to actually use the 3dnow instructions? Does this mean

Re: HEADS UP: SSE instructions (Re: cvs commit: src/share/mk bsd.cpu.mk)

2002-09-06 Thread Kris Kennaway
On Fri, Sep 06, 2002 at 09:49:41PM -0400, Kenneth Culver wrote: I assume the compiler is not stupid enough to try and use both when that is impossible. Don't forget this is all just passing a CPU name to gcc which actually decides what instructions to use. That's not what I mean... What

Re: HEADS UP: SSE instructions (Re: cvs commit: src/share/mk bsd.cpu.mk)

2002-09-06 Thread Peter Wemm
Kenneth Culver wrote: I assume the compiler is not stupid enough to try and use both when that is impossible. Don't forget this is all just passing a CPU name to gcc which actually decides what instructions to use. That's not what I mean... What I mean is that if one application is

Re: HEADS UP: SSE instructions (Re: cvs commit: src/share/mk bsd.cpu.mk)

2002-09-06 Thread David O'Brien
On Fri, Sep 06, 2002 at 09:28:28PM -0400, Kenneth Culver wrote: Note that you'll need to have 'options CPU_ENABLE_SSE' in your kernel configuration file if you have a SSE-capable CPU, otherwise you'll get SIGILL from certain applications (e.g. ncurses) What if you don't want to do this