From owner-freebsd-hackers@FreeBSD.ORG  Tue Mar 29 07:23:21 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1BAFD16A4CE
	for <hackers@freebsd.org>; Tue, 29 Mar 2005 07:23:21 +0000 (GMT)
Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 832F543D5A
	for <hackers@freebsd.org>; Tue, 29 Mar 2005 07:23:20 +0000 (GMT)
	(envelope-from dleimbac@gmail.com)
Received: by rproxy.gmail.com with SMTP id j1so1518426rnf
        for <hackers@freebsd.org>; Mon, 28 Mar 2005 23:23:20 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=n7kpm7M0Xj8AfXgLzLDnEWCayFgwo4FpWk27xUwjIinHpDpIhOePzX6U+Gl7WwEMNWwZO4WPn+SR48FpBzzGnriwwfayJgcr4zisxXW1UoSDPYgKUzzWOOPInsXo2OZDBPKQZHy9Z4XzeJHMsN/e9GUO3Y9iFju1JB1s9XjzzSo=
Received: by 10.38.126.32 with SMTP id y32mr3144849rnc;
        Mon, 28 Mar 2005 23:23:19 -0800 (PST)
Received: by 10.38.82.48 with HTTP; Mon, 28 Mar 2005 23:23:19 -0800 (PST)
Message-ID: <5bbfe7d405032823232103d537@mail.gmail.com>
Date: Mon, 28 Mar 2005 23:23:19 -0800
From: David Leimbach <dleimbac@gmail.com>
To: hackers@freebsd.org
In-Reply-To: <5bbfe7d405032823144fc1af7b@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <423C15C5.6040902@fsn.hu>
	<20050327133059.3d68a78c@Magellan.Leidinger.net>
	<20050327134044.GM78512@silverwraith.com>
	<20050327162839.2fafa6aa@Magellan.Leidinger.net>
	<5bbfe7d405032823144fc1af7b@mail.gmail.com>
Subject: Fwd: 5-STABLE kernel build with icc broken
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: David Leimbach <dleimbac@gmail.com>
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2005 07:23:21 -0000

meant to send this to the list too... sorry
> Are you implying DragonFly uses FPU/SIMD?  For that matter does any kernel?

I believe it does use SIMD for some of it's fast memcopy stuff for
it's messaging system
actually.  I remember Matt saying he was working on it.

http://leaf.dragonflybsd.org/mailarchive/kernel/2004-04/msg00262.html

If you can manage the alignment issues it can be a huge win.

Dave
>
> Thanks,
> jason
>
> > - optimizations for Intel CPUs direct from the manufacturer of the CPU
> >   (they have a lot of interest to produce very fast code)
> > - a different set of compiler warnings
> > - better code quality (if is compilable by more than one compiler it
> >   may be more portable)
> >
> >Icc already pointed out some bad code (asm code in the IP checksumming
> >code... DragonFly changed it already), and the panic as noticed above
> >may also be an indication that we have some code in the tree which
> >smells bad.
> >
> >Bye,
> >Alexander.
> >
> >
> >
>
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
>