From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCHES] gnu: linux-libre: Full retpoline support on x86 [spectre mitigation] Date: Mon, 22 Jan 2018 15:51:37 -0500 Message-ID: <20180122205137.GB12556@jasmine.lan> References: <87po648e2n.fsf@netris.org> <87tvvexw4a.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rJwd6BRFiFCcLxzm" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36508) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edj4A-0005CW-Ld for guix-devel@gnu.org; Mon, 22 Jan 2018 15:51:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1edj47-000139-Fn for guix-devel@gnu.org; Mon, 22 Jan 2018 15:51:42 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:51003) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1edj47-00012s-AZ for guix-devel@gnu.org; Mon, 22 Jan 2018 15:51:39 -0500 Content-Disposition: inline In-Reply-To: <87tvvexw4a.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Chris Marusich Cc: guix-devel@gnu.org --rJwd6BRFiFCcLxzm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 21, 2018 at 10:09:41PM -0800, Chris Marusich wrote: > Mark H Weaver writes: >=20 > > Here are two patches that: > > > > * Add gcc-7.3.0-RC-20180117, which includes support for retpoline. > > * Use gcc-7.3 to build linux-libre on x86 systems. >=20 > Awesome! Thank you for this. >=20 > > My question is: should we push these patches to 'master' now, or should > > we wait until gcc-7.3 is released (possibly as soon as January 24)? >=20 > Since GuixSD makes it easy to roll back the entire system if it turns > out there's a problem with the new kernel, I think we should just do it. Agreed, the risk seems low. The only issue is that we (and anyone not using substitutes) will have to build GCC 7 and linux-libre twice in a short period of time, which could be annoying. However, I don't have experience with GCC release candidates; I assume they are of high quality. --rJwd6BRFiFCcLxzm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlpmTtkACgkQJkb6MLrK fwh4hA/+Lhz/pdtpSwtFjYaJ6thc/RrldfzP45RYWhaac4/3//zxqR0RfH8w772h g/8+xfoE+kOJSVLOR56RsedYFYYu2Y3hQUt4PakH244WSO0Z+JYIXd1r5RfA0mmk uBYpKOK2WUVS8rKTYydtJOrZU87QIk8wS9m8XJMxd51vinlwwctM+DyZdV/IMC8J 5iHvgwb5pJsjEFLzfHnoqtLBWtLbxaPXlbfNMkWDzzueCd2HSOg87a65nL0SxwU/ vR6nTQfqa7TlJqcJ6HupsvNBe1Hu0mz/j2p3ZpnXlf9C2CtajQoGdFEwz3TUUvnD dyiyQYUQ0u3XxzvVGXqmCrzUPuN/NV/qNwrVmtjaFDdd0cNdoys/i+PKzwZ7PTbv RNJtzxGSWuV9+gK+kCI9NPV03GxqZcvbDbGPevvITVO+oSNE5FbEj6m4MInbCHHC 3IfRxX7xG5PXfG7Ci5MhNDJG+ULvp+LMEKSLJZl3N0/72nZXtaQmIRRo/n+VKknH 3iBrWBbQ6gbw3TzHywL7TRvdgflS6OjuI32N4BlgA9YKXzFVTLtc7qTgmU6Wpt+l RYExCmMaBpS6sx5CA0ip91ZYlnrDdtBkgTcd35Zhu2Kso/34vSODpLuE8WRY9Lxy UfTH1rTrqWMLcf8LNbLfK4Xa2mwHOqtgfmYMq8K1UvC0w5ArByQ= =Ef15 -----END PGP SIGNATURE----- --rJwd6BRFiFCcLxzm--