From owner-freebsd-arch@freebsd.org Sat Oct 5 17:34:15 2019 Return-Path: Delivered-To: freebsd-arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C8CEE138A9C for ; Sat, 5 Oct 2019 17:34:15 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46lv4Q3jfWz3xm5 for ; Sat, 5 Oct 2019 17:34:14 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qt1-x836.google.com with SMTP id u40so13251897qth.11 for ; Sat, 05 Oct 2019 10:34:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JKJE8CSbdL1kbtlIRlCTpounZIQkBNKNvy979si0qBM=; b=gsqPU698zO1GYlrQX2M5r9R+qNnGFdRneMDJeyUhE3GPQmuKhtLXteVAv0NJXcop0X A8CX992NUquRq1+MYFTmbfJPxyl3/J9viw4Ez13NLjtxUqvjKkvwEJlBJ3Nkwp+EsGUr sswy95YgjwBGlkqTQ6vYZBQTDL3CRx9bVWEIrATDal+T1Cjb3RIrIyA/Xb7nuzXxENYu 66Wfw8LxpT8c4ZsxUIAEkBYsRSCjXFGYo1oh/pQOomqeP9opMxTTV1QC5by4y3Cuo5Uv 9Y9o9cgUawuFgAmf8KMnNETlpcIeQP9M6zRr2dx574cODRAwMdJN9FzH2BIAg88KSbR/ D7bw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=JKJE8CSbdL1kbtlIRlCTpounZIQkBNKNvy979si0qBM=; b=m0c7H8/SuymWOo3LOVLBIB9LXSTsMiU7EwvbiHmFQ0ntzjkpdxkx5wDcwuylp9vtfG 7JAbnOGciL9o0M5IC4F0Vm8cIfSwIn46Q5nBBDF4/XbgKxR1RUi/jL3sMPMTEAZqUu+P 612shfa/594r8ZPONWyHZHMe37IxgYWLrD96gcXo+USSY6f6VOAqq3big+4tSWRyg8NJ C1505lYiaIvfQQtoGypygvoRAvaOJYqcOZK47KhbIJ/XWDD7Mm/F3N8hDFRZHZ8454B8 hfFZQsErxPE+iFP+WdjyE8GiEdZzsOmecnNksd5Q93J8gHUk91zecY2tIqS1badXhhtJ bqOA== X-Gm-Message-State: APjAAAW5Iu634o8yIfYJ7y0uHWyIryPkJUW30Lx2VScNFymcOuhMPbiA gvnwmsnpRDpY0ALu9+VppzeAWA== X-Google-Smtp-Source: APXvYqyWOzJXfeUbNS17gbPEsJ5q+C48S8jW9NCiucNw1/Y3ufUKZ6Eu5HT0mYYO+djR+eTskCptdA== X-Received: by 2002:ac8:6696:: with SMTP id d22mr22492396qtp.21.1570296852938; Sat, 05 Oct 2019 10:34:12 -0700 (PDT) Received: from mutt-hbsd (pool-100-16-231-224.bltmmd.fios.verizon.net. [100.16.231.224]) by smtp.gmail.com with ESMTPSA id b1sm3989136qtr.17.2019.10.05.10.34.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 05 Oct 2019 10:34:12 -0700 (PDT) Date: Sat, 5 Oct 2019 13:34:11 -0400 From: Shawn Webb To: Warner Losh Cc: freebsd-arch@freebsd.org Subject: Re: New CPUTYPE default for i386 port Message-ID: <20191005173411.l6gs3kszs7zcgfey@mutt-hbsd> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="22iic2qs5ebepwwt" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD mutt-hbsd 13.0-CURRENT-HBSD FreeBSD 13.0-CURRENT-HBSD r352488+2a20025064d4-c272097(hardened/current/master) HARDENEDBSD-13-CURRENT amd64 X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0xFF2E67A277F8E1FA User-Agent: NeoMutt/20180716 X-Rspamd-Queue-Id: 46lv4Q3jfWz3xm5 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=hardenedbsd.org header.s=google header.b=gsqPU698; dmarc=none; spf=pass (mx1.freebsd.org: domain of shawn.webb@hardenedbsd.org designates 2607:f8b0:4864:20::836 as permitted sender) smtp.mailfrom=shawn.webb@hardenedbsd.org X-Spamd-Result: default: False [-6.91 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[hardenedbsd.org:s=google]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[hardenedbsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[hardenedbsd.org:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[6.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-2.81)[ip: (-9.26), ipnet: 2607:f8b0::/32(-2.56), asn: 15169(-2.15), country: US(-0.05)]; RECEIVED_SPAMHAUS_PBL(0.00)[224.231.16.100.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 17:34:15 -0000 --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--