From owner-freebsd-arch@FreeBSD.ORG Fri Oct 5 15:54:48 2012 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77C06106566B; Fri, 5 Oct 2012 15:54:48 +0000 (UTC) (envelope-from uqs@FreeBSD.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 061928FC0A; Fri, 5 Oct 2012 15:54:47 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.5/8.14.5) with ESMTP id q95FsfgR072978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 5 Oct 2012 17:54:41 +0200 (CEST) (envelope-from uqs@FreeBSD.org) Date: Fri, 5 Oct 2012 17:54:41 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Dag-Erling =?utf-8?B?U23DuHJncmF2?= Message-ID: <20121005155441.GL69724@acme.spoerlein.net> Mail-Followup-To: Dag-Erling =?utf-8?B?U23DuHJncmF2?= , Garrett Cooper , Konstantin Belousov , Dimitry Andric , Andriy Gapon , freebsd-arch@freebsd.org References: <506C385C.3020400@FreeBSD.org> <506DEB4C.5020508@andric.com> <86haq9hq2c.fsf@ds4.des.no> <20121005033244.GL35915@deviant.kiev.zoral.com.ua> <86y5jll7kc.fsf@ds4.des.no> <86txu9l4z9.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86txu9l4z9.fsf@ds4.des.no> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Garrett Cooper , Konstantin Belousov , Dimitry Andric , Andriy Gapon , freebsd-arch@FreeBSD.org Subject: Re: x86 boot code build X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2012 15:54:48 -0000 On Fri, 2012-10-05 at 10:04:26 +0200, Dag-Erling Smørgrav wrote: > Garrett Cooper writes: > > I would target the appropriate architecture (amd64) where it matters > > (amd64), and target the lowest sane common denominator on i386. In > > reality, what does a couple MB mean on amd64 vs i386? > > 1) Nobody mentioned amd64 - this is about i386. > > 2) It's not a question of *size* but of *performance*. By targeting the > least capable platform that our users are likely to encounter > (pentium-mmx) instead of one which is virtually eradicated (486), we > can use features that are available on the former but not the latter. > > Someone said they'd like to target SSE2, but that would leave many > common embedded systems out in the cold. If we do that, we should > provide two sets of binaries; one set for sse2-capable machines > (which covers all i386 desktop and server machines made in the last > ten years) and one set for pentium-mmx (which covers the soekris and > other popular SFF / embedded systems). Seriously? How about we leave i386 as is for the embedded folks and just move forward with amd64. Any improvements made on our i386 support are useless to about 98% of our users. It's 2012 people ... kthxbai Uli