From owner-freebsd-hackers Thu Oct 14 2:32:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 789B014DB3 for ; Thu, 14 Oct 1999 02:32:21 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id MAA59639; Thu, 14 Oct 1999 12:32:14 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Thu, 14 Oct 1999 12:32:14 +0300 (EEST) From: Narvi To: Ollivier Robert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: --enable-haifa In-Reply-To: <19991014002843.A64703@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Oct 1999, Ollivier Robert wrote: > According to W Gerald Hicks: > > Just curious what effect using the --enable-haifa flag for building > > gcc-2.95.1/x86 would have so I did a comparison using the Dhrystone > > benchmark from /usr/ports/benchmarks/bytebench. > > I think the Haifa scheduler is only really effective on pure RISC processors > like the Alpha or PA-8000. I remember doing some tests with older versions of > egcs and not seeing any significant changes... According to my vague recollectiosn from the early times of egcs when faifa was integrated, etc. part of the problem is that to have haifa be really effective, all old kluges need be removed... Something that back then happened/had happened only to a few cpus, like HP-PA. Not sure what may have happened since, but I doubt somebody has redone x86 code generation and fully integrated haifa ins scheduler. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message