From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: JonY <10walls@gmail.com>, NightStrike <nightstrike@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] gcc-8/porting_to.html
Date: Thu, 04 May 2017 14:43:00 -0000 [thread overview]
Message-ID: <f9d3fbd0-1b5b-3edd-759d-d4f4e88b9a8c@foss.arm.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1703230746100.2433@anthias.pfeifer.com>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Committed with the suggested changes (see attachment for reference).
Thanks.
Best regards,
Thomas
On 23/03/17 06:47, Gerald Pfeifer wrote:
> Hi Thomas,
>
> On Wed, 22 Mar 2017, Thomas Preudhomme wrote:
>> Is this ok for wwwdocs once [1] is committed in GCC 8 cycle?
>
> + <li>GCC on Microsoft Windows can now be configured via
> + <code>--enable-mingw-wildcard</code> or
> + <code>--disable-mingw-wildcard</code> to force a specific behavior for
> + GCC itself with regards to supporting or not the wildcard character.
>
> Here I would omit the "or not" which I believe does not work well
> in English.
>
> + Prior versions of GCC would follow the configuration of MinGW runtime.
>
> And here add "the" before "MinGW".
>
> This looks fine to me with these two minor changes, thank you.
>
> Gerald
[-- Attachment #2: document_windows_wildcard_change_gcc8.patch --]
[-- Type: text/x-patch, Size: 1054 bytes --]
Index: htdocs/gcc-8/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.2
diff -u -r1.2 changes.html
--- htdocs/gcc-8/changes.html 12 Mar 2017 14:25:34 -0000 1.2
+++ htdocs/gcc-8/changes.html 23 Mar 2017 10:44:35 -0000
@@ -135,7 +135,16 @@
<!-- <h3 id="vxmils">VxWorks MILS</h3> -->
-<!-- <h3 id="windows">Windows</h3> -->
+<h3 id="windows">Windows</h3>
+ <ul>
+ <li>GCC on Microsoft Windows can now be configured via
+ <code>--enable-mingw-wildcard</code> or
+ <code>--disable-mingw-wildcard</code> to force a specific behavior for
+ GCC itself with regards to supporting the wildcard character. Prior
+ versions of GCC would follow the configuration of the MinGW runtime.
+ This behavior can still be obtained by not using the above options or by
+ using <code>--enable-mingw-wildcard=platform</code>.</li>
+ </ul>
<!-- .................................................................. -->
next prev parent reply other threads:[~2017-05-04 14:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 9:49 [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows Thomas Preudhomme
2017-01-19 2:05 ` JonY
2017-01-20 9:06 ` Thomas Preudhomme
2017-01-26 13:19 ` Thomas Preudhomme
2017-02-07 8:48 ` JonY
2017-02-14 9:46 ` Thomas Preudhomme
2017-02-14 10:58 ` JonY
2017-02-17 11:01 ` JonY
2017-02-17 11:51 ` Thomas Preudhomme
2017-02-17 23:05 ` JonY
2017-02-22 16:07 ` Thomas Preudhomme
[not found] ` <CAF1jjLtsw10najrRwzJ7MJSSKxqmX0Wy4gKyf=dhmcAebS+JOA@mail.gmail.com>
2017-03-02 16:58 ` Thomas Preudhomme
2017-03-04 14:25 ` [wwwdocs] gcc-8/porting_to.html (was: [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows) Gerald Pfeifer
2017-03-09 10:51 ` [wwwdocs] gcc-8/porting_to.html Thomas Preudhomme
2017-03-09 10:59 ` Jakub Jelinek
2017-03-09 11:22 ` Thomas Preudhomme
2017-03-09 13:16 ` JonY
2017-03-12 14:08 ` Gerald Pfeifer
2017-03-12 23:51 ` JonY
2017-03-22 17:39 ` Thomas Preudhomme
2017-03-22 22:51 ` JonY
2017-03-23 6:47 ` Gerald Pfeifer
2017-03-23 10:47 ` Thomas Preudhomme
2017-05-04 11:10 ` JonY
2017-05-04 14:37 ` Thomas Preudhomme
2017-05-04 14:43 ` Thomas Preudhomme [this message]
2017-05-04 15:17 ` [arm-embedded] [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows Thomas Preudhomme
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9d3fbd0-1b5b-3edd-759d-d4f4e88b9a8c@foss.arm.com \
--to=thomas.preudhomme@foss.arm.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=nightstrike@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).