cvs commit: src/share/mk bsd.cpu.mk bsd.dep.mk bsd.lib.mk bsd.sys.mk src/sys/conf files kern.mk kern.pre.mk kmod.mk src/sys/dev/aic7xxx/aicasm Makefile

[David O'Brien]

On Mon, Mar 15, 2004 at 06:03:24PM +0100, Alexander Leidinger wrote:
> > >   Problems with icc v8:
> > >    - panic: npx0 cannot be emulated on an SMP system
> > >    - UP: first start of /bin/sh results in a FP exception
> > 
> > You forgot the other problems with icc v8 -- Intel's preditorial
> > behavior.  Note that some parts of the Intel compilers support libs do a
> > CPUID call and if it notes an AMD CPU either segfaults or dumbs down the
> > capabilities of the CPU to that of the original i386.
> 
> AFAIK: 
>  - only if the compiled binary contains the main function
>    (the kernel doesn't)
>  - only if you use a specific compiler option, which I don't use here

It happens in several circumstances, not just when using one particular
compiler option.
 
> To circumvent this I suggest to read
> http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&oe=UTF-8&group=comp.arch&selm=a13e403a.0402091438.14018f5a%40posting.google.com
> 
> BTW.: AFAIK it doesn't segfault, it exit()s.

BTW, icc v8 produced binaries will sometimes segfault on AMD processors.
Trust me, AMD has tested this issue more than you have.
 
> Any manufacturer is free to limit the use of his programs as he wants. I
> agree, this behavior isn't nice, but life isn't nice either (sometimes).

Then I'd like to take the stance of reanble the blind use of EFER.NXE in
the FreeBSD/amd64 loader -- Intel ia32e can just add that feature.

-- 
-- David  (obrien at FreeBSD.org)