New CPUTYPE default for i386 port

[Shawn Webb]

On Sat, Oct 05, 2019 at 09:28:53AM -0600, Warner Losh wrote:
> For a variety of reasons,  the time has come to change the default code
> generation arch from i486 to i686 on our i386 port. No actual code removal
> is planned as part of this effort. Only the default is doing changed for
> clang.
> 
> The practical upshot of this for our i386 users will be zero for almost
> everybody. For the tiny sliver of people planning to deploy FreeBSD on a
> i486 or i586 core, a simple addition of CPUTYPE=xxxx to /etc/make.conf is
> all that is needed for the src side of things. They will need to setup
> their own poudriere instance and create their own pkg repo to build
> whatever packages are required for their deployment.
> 
> It's my belief that even in the trailing edge long tail embedded deployment
> segment of our user base this will cause no issues. All deployments there
> I'm aware of have moved of i486 class CPUs and the one 586 class core
> deployment I know of has no plans to update that to FreeBSD 11, let alone
> newer.
> 
> There are a number of advantages to doing this which have been articulated
> at length in other discussions. Briefly we get better code generation for
> CPUs people use and we avoid some test failures in llvm 9.0 because i486
> doesn't have 64-bot atomics.
> 
> Comments?

Full disclosure: I personally don't care about 32-bit architectures.
Feel free to ignore me based on that. ;-)

I'm curious about the possibilities regarding 64-bit time_t on 32-bit
Intel systems.

Thanks,

-- 
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

Tor-ified Signal:    +1 443-546-8752
Tor+XMPP+OTR:        lattera at is.a.hacker.sx
GPG Key ID:          0xFF2E67A277F8E1FA
GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9  3633 C85B 0AF8 AB23 0FB2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20191005/c7bfece4/attachment.sig>