Date: Sun, 28 Jul 2002 16:14:25 +0200 From: Bernd Walter <ticso@cicely5.cicely.de> To: "David O'Brien" <obrien@FreeBSD.org>, John Baldwin <jhb@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/mk bsd.cpu.mk Message-ID: <20020728141424.GH97768@cicely5.cicely.de> In-Reply-To: <20020728033812.GA86714@dragon.nuxi.com> References: <200207272204.g6RM46Ji040820@freefall.freebsd.org> <20020727221313.C48442A7D6@canning.wemm.org> <20020728033812.GA86714@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 27, 2002 at 08:38:12PM -0700, David O'Brien wrote: > On Sat, Jul 27, 2002 at 03:13:13PM -0700, Peter Wemm wrote: > > > This defaults to tuning i386 builds for i686 machines though not using > > > any instructions that aren't found on an 80386. For alpha it defaults > > > to tuning for an EV5. > > EV56 please. Maybe even EV6. ev56 will break compatibility with many supported older machines. What happens with releases and packages? This situation is a bit different than loosing 80386 support in the binaries where we can expect owners to have acces to at least a pentium to build the binaries their self. Please add at least a note in UPDATING so non BWX owners don't forget to update their /etc/make.conf. EV6 would be a bad default as it includes Multimedia extensions which are not available on ev56 machines and exclude much more machines without such a big performance win. Also it would break kernel builds as we explicitly tell the assembler to understand ev56 assembly - maybe it's a good idea to just raise that. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020728141424.GH97768>