Date: Tue, 29 Mar 2005 13:23:09 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: jason henson <jason@ec.rr.com> Cc: hackers@freebsd.org Subject: Re: 5-STABLE kernel build with icc broken Message-ID: <20050329132309.v3ylwk2pesk8g80c@netchild.homeip.net> In-Reply-To: <4248B723.80907@ec.rr.com> References: <423C15C5.6040902@fsn.hu> <20050327133059.3d68a78c@Magellan.Leidinger.net> <20050327134044.GM78512@silverwraith.com><4248B723.80907@ec.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
jason henson <jason@ec.rr.com> wrote:
> >Various:
> > - auto-vectorizer (no benefit for the kernel, since we can't use >
> FPU/SIMD instructions at any time... yet (interested hackers can
> > have a look how DragonFly handles it, I can provide the necessary
> > commit logs))
> > >
> Are you implying DragonFly uses FPU/SIMD? For that matter does any kernel?
AFAIK DragonFly _allows_ code to use the FPU/SIMD in the kernel. And AFAIR
they use SIMD in b{copy,zero} (we do this too, but we do this is in a
"controlled environment" whereas DFly just allows the use of FPU/SIMD in an
"use as you like" manner everywhere).
Bye,
Alexander.
--
http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Closet extrovert.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050329132309.v3ylwk2pesk8g80c>