From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24840 invoked by alias); 12 Mar 2017 14:08:02 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 24818 invoked by uid 89); 12 Mar 2017 14:08:01 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: ainaz.pair.com Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 12 Mar 2017 14:08:00 +0000 Received: from anthias (vie-188-118-249-200.dsl.sil.at [188.118.249.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id D52683F531; Sun, 12 Mar 2017 10:07:56 -0400 (EDT) Date: Sun, 12 Mar 2017 14:08:00 -0000 From: Gerald Pfeifer To: Thomas Preudhomme cc: JonY <10walls@gmail.com>, NightStrike , gcc-patches@gcc.gnu.org Subject: Re: [wwwdocs] gcc-8/porting_to.html In-Reply-To: <20845b34-f951-f2d1-0365-b8c8e788be5b@foss.arm.com> Message-ID: References: <3c3cd900-7d38-a66d-d306-12c968d26f0b@gmail.com> <35f8542e-df08-62ac-da0e-824a974b96e6@foss.arm.com> <7aaf616d-2e0a-cf68-3e4b-0c48b6e16d00@foss.arm.com> <97780aa1-62c2-9471-a9f7-fce968f94fe3@gmail.com> <20845b34-f951-f2d1-0365-b8c8e788be5b@foss.arm.com> MIME-Version: 1.0 Content-Type: text/plain; CHARSET=US-ASCII; FORMAT=flowed X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00609.txt.bz2 On Thu, 9 Mar 2017, Thomas Preudhomme wrote: > JonY: what about the attached patch to document the change of behavior > of GCC on Windows depending on the configure option used? +

MinGW issues

+ +

GCC on Microsoft Windows can now be configured via +--enable-mingw-wildcard or --disable-mingw-wildcard +to force a specific behavior for GCC itself with regards to supporting or +not the wildcard character. Prior versions of GCC would follow the Perhaps put "(or not)" in parentheses? +configuration of MinGW runtime. This behavior can still be obtained by not +using the above options or by using +--enable-mingw-wildcard=platform.

Is this really going to be a question for the Porting Guide, or more something you'd put into the release notes (aka changes.html)? I am thinking more the latter. This patch is approved for gcc-8/changes.html once GCC 7 has branched and gcc-8/changes.html be put in place (though I may be doing that pro- actively later today ;-). Gerald