From owner-freebsd-arch@freebsd.org Wed Oct 11 22:44:51 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09EEFE391F5 for ; Wed, 11 Oct 2017 22:44:51 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF628803BC; Wed, 11 Oct 2017 22:44:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 29E69C85; Wed, 11 Oct 2017 17:44:49 -0500 (CDT) Date: Wed, 11 Oct 2017 17:44:48 -0500 From: Mark Linimon To: Warner Losh Cc: Nathan Whitehorn , "freebsd-arch@freebsd.org" Subject: Re: Making C++11 a hard requirement for FreeBSD Message-ID: <20171011224447.GB7664@lonesome.com> References: <2116882.XEKuxOb729@ralph.baldwin.cx> <20171006072010.ygq3k5ygwxykk4nb@ivaldir.net> <577d3900-76f2-2c52-8ada-b8fb1fe881be@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 22:44:51 -0000 On Mon, Oct 09, 2017 at 11:56:07PM -0600, Warner Losh wrote: > However, absent a clear plan, as well as resourced dedicated to realize it, > I'm not sure that we should block things further based strictly on a list > of things that are broken. If there's a plan to fix, I'm willing to defer > to give that plan a chance to happen. In the absence of a specific plan > with timelines, I'm reluctant to indefinitely delay the negotiated plan > for 12 which has taken years to pull together. Otherwise, is 3 more months > enough? Is 6? are 12? Do we wait for FreeBSD 13? Even though I work on both affected archs, I think gcc4.2.1 in base has to be _gone_ for 12. It's time. Here's my compromise suggestion. We give nathan (and myself and whoever else wants to help) until the BSDCan Devsummit to fix this. But at that point it's the Danish Axe(*) no matter what state it's in. Period. That gives us an absolute deadline. For reference, gjb has guesstimated that the 12.0 release cycle will begin around February 2019. (good grief I nearly typed 2109. stahp.) In any case, axing things during the Devsummit is a Grand Tradition at this point. Why not continue it? :-) mcl * or Wemm axe, or Losh axe, or whatever