Date: Sat, 5 Oct 2019 13:34:11 -0400 From: Shawn Webb <shawn.webb@hardenedbsd.org> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-arch@freebsd.org Subject: Re: New CPUTYPE default for i386 port Message-ID: <20191005173411.l6gs3kszs7zcgfey@mutt-hbsd> In-Reply-To: <CANCZdfoFPsjyuCTfm0dQhz%2BsgVHLEvMA8-E3-Yhciz67qdoKvw@mail.gmail.com> References: <CANCZdfoFPsjyuCTfm0dQhz%2BsgVHLEvMA8-E3-Yhciz67qdoKvw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--22iic2qs5ebepwwt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > 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=3Dxxxx 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. >=20 > It's my belief that even in the trailing edge long tail embedded deployme= nt > 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. >=20 > 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. >=20 > 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, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0xFF2E67A277F8E1FA GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 --22iic2qs5ebepwwt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAl2Y1AoACgkQ/y5nonf4 4forYg//bYjJ3YcFYG18R+ZAWCVNXYOxf0N6GJTZoilAbosgRU9JWRQFgiyxc9gy C38BTcG8ydZh38pls9fJQF5htqokFxu2xhK8Nw4XGhmyScK/XdiUcUMXIDSFRygA DxEQsr5Um5d+rEIt7pqBBN4fiVBHT95h6MnhI0hVcoxSubDK2sO0OPT1GvoLcq+E /m3koORJOEWbGlNKjb9NuvUgqLAQiH3GxgC5vmlVZQlZmEFC4p7HYhHow4NWi7SX HNCEXE5M7hzMVbdXvQRc/5uAF5KU5dsj51CU0rzuDZ/uAzluZX46S5TI69R1dp2B fE3T84CxTEAb34hcGIZOcKgEnHPCYdA1fpBfCbvjIZRQ/3stzERCcLRiJCdjOAXY RWU24agyNoS6rjiCvGho2TbU6jpY+tSo+kuTbvCGWgSYto3Zb0X90nUYCLK8Vp9r cLEIanN/5C5y9GAjfkdTH4FwnlEWHl9pthZ0w9GacpaAE5lxIQKez3SSWrGb1zT7 vYKaOygOb4KU4cECxwDJdTBCWcWqLJQa0K82Qf+FONrzGbfJoPXeoyalCEcB5Jjq poaaMOtyelW4N1rfrsyXAt6AslWx2Ezv7RFFyI+I/p2JkESGp3Zn888dk0naqm4C nTEZcbREHzS6ORNOBVS9A76HtbjUDvoSafvORExflCGHeJ/VeyA= =niQ1 -----END PGP SIGNATURE----- --22iic2qs5ebepwwt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191005173411.l6gs3kszs7zcgfey>