Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Nov 2011 22:52:02 +0100
From:      Dimitry Andric <dim@FreeBSD.org>
To:        src-committers@freebsd.org, svn-src-all@freebsd.org,  svn-src-head@freebsd.org
Subject:   Re: svn commit: r227538 - head/tools/build
Message-ID:  <4EC2DF02.7030602@FreeBSD.org>
In-Reply-To: <20111115211449.GA476@zim.MIT.EDU>
References:  <201111152015.pAFKFwqb015331@svn.freebsd.org> <4EC2CFDD.7070206@FreeBSD.org> <20111115211449.GA476@zim.MIT.EDU>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2011-11-15 22:14, David Schultz wrote:
> On Tue, Nov 15, 2011, Dimitry Andric wrote:
>> Note all the final executables will use 'real' atomic operations.  That
>> is, unless you compile with CPUTYPE?=i386, and I wish you the best of
>> luck in that case, you'll need it. :)
> 
> I thought we dropped support for anything less than a 486DX years ago.

Well, theoretically you could still attempt to build for i386, but it is
almost sure to have bitrotted beyond any working state.  The CPUTYPE
stuff in bsd.cpu.mk still seems to support it, as does gcc itself, of
course.  And as mentioned in the commit message, until 2 years ago, the
default CPU for gcc was i386; which is the only reason for this commit.

Indeed, I386_CPU support was removed from GENERIC more than 10 years
ago, in r71025.  But even there it says:

"Remove I386_CPU from GENERIC.  Support for the 386 seriously pessimizes
performance on other x86 processors.  Custom kernels can still be built
that will run on the 386."

I wonder if that's still true... maybe it is time to really clean up any
pre-i486 leftovers. :)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EC2DF02.7030602>