From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hamza.pair.com (hamza.pair.com [209.68.5.143]) by sourceware.org (Postfix) with ESMTPS id A5E8C384242B; Tue, 1 Dec 2020 21:58:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A5E8C384242B Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pfeifer.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gerald@pfeifer.com Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id 1B88933EF0; Tue, 1 Dec 2020 16:58:16 -0500 (EST) Received: from [192.168.1.5] (77.118.226.34.wireless.dyn.drei.com [77.118.226.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hamza.pair.com (Postfix) with ESMTPSA id 7CD0633EEF; Tue, 1 Dec 2020 16:58:15 -0500 (EST) Date: Tue, 1 Dec 2020 22:58:04 +0100 (CET) From: Gerald Pfeifer To: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org Subject: Re: [wwwdocs] Document libstdc++ header dependency changes In-Reply-To: <20201126115337.GK1312820@redhat.com> Message-ID: References: <20201126113309.GA2103723@redhat.com> <20201126115337.GK1312820@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libstdc++@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++ mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2020 21:58:17 -0000 On Thu, 26 Nov 2020, Jonathan Wakely via Gcc-patches wrote: >> Also explain how to replace dynamic exception specifications. > And a small correction. Ah, I was going to point that out. :-) Let's see how many ports/packages the header cleanup is going to break this time. Updating the default version of GCC in FreeBSD has proven a painful endeavour the last few times (though the GCC 10 update is mostly delayed due to stricter behavior on the Fortran side). Cheers, Gerald