From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: Gerald Pfeifer <gerald@pfeifer.com>, JonY <10walls@gmail.com>
Cc: NightStrike <nightstrike@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] gcc-8/porting_to.html
Date: Thu, 09 Mar 2017 10:51:00 -0000 [thread overview]
Message-ID: <20845b34-f951-f2d1-0365-b8c8e788be5b@foss.arm.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1703041520500.2487@anthias.pfeifer.com>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
Thanks Gerald,
JonY: what about the attached patch to document the change of behavior of GCC on
Windows depending on the configure option used?
Best regards,
Thomas
On 04/03/17 14:25, Gerald Pfeifer wrote:
> On Thu, 2 Mar 2017, Thomas Preudhomme wrote:
>>> This should be mentioned in the "porting to" page when it eventually
>>> goes in, as it may be surprising behavior.
>> Will do once the file is created for gcc-8. Thanks for the suggestion
>
> Here we go. :-) Applied.
>
> Gerald
>
> Index: porting_to.html
> ===================================================================
> RCS file: porting_to.html
> diff -N porting_to.html
> --- /dev/null 1 Jan 1970 00:00:00 -0000
> +++ porting_to.html 4 Mar 2017 14:20:46 -0000
> @@ -0,0 +1,37 @@
> +<html>
> +
> +<head>
> +<title>Porting to GCC 8</title>
> +</head>
> +
> +<body>
> +<h1>Porting to GCC 8</h1>
> +
> +<p>
> +The GCC 8 release series differs from previous GCC releases in
> +<a href="changes.html">a number of ways</a>. Some of these are a result
> +of bug fixing, and some old behaviors have been intentionally changed
> +to support new standards, or relaxed in standards-conforming ways to
> +facilitate compilation or run-time performance.
> +</p>
> +
> +<p>
> +Some of these changes are user visible and can cause grief when
> +porting to GCC 8. This document is an effort to identify common issues
> +and provide solutions. Let us know if you have suggestions for improvements!
> +</p>
> +
> +
> +<h2 id="cpp">Preprocessor issues</h2>
> +
> +
> +<h2 id="c">C language issues</h2>
> +
> +
> +<h2 id="cxx">C++ language issues</h2>
> +
> +
> +<h2 id="links">Links</h2>
> +
> +</body>
> +</html>
>
[-- Attachment #2: document_windows_wildcard_change_gcc8.patch --]
[-- Type: text/x-patch, Size: 3579 bytes --]
cvs diff: Diffing .
cvs diff: Diffing bin
cvs diff: Diffing cgi-bin
cvs diff: Diffing htdocs
cvs diff: Diffing htdocs/benchmarks
cvs diff: Diffing htdocs/bugs
cvs diff: Diffing htdocs/bzkanban
cvs diff: Diffing htdocs/egcs-1.0
cvs diff: Diffing htdocs/egcs-1.1
cvs diff: Diffing htdocs/fortran
cvs diff: Diffing htdocs/gcc-2.95
cvs diff: Diffing htdocs/gcc-3.0
cvs diff: Diffing htdocs/gcc-3.1
cvs diff: Diffing htdocs/gcc-3.2
cvs diff: Diffing htdocs/gcc-3.3
cvs diff: Diffing htdocs/gcc-3.4
cvs diff: Diffing htdocs/gcc-4.0
cvs diff: Diffing htdocs/gcc-4.1
cvs diff: Diffing htdocs/gcc-4.2
cvs diff: Diffing htdocs/gcc-4.3
cvs diff: Diffing htdocs/gcc-4.4
cvs diff: Diffing htdocs/gcc-4.5
cvs diff: Diffing htdocs/gcc-4.6
cvs diff: Diffing htdocs/gcc-4.7
cvs diff: Diffing htdocs/gcc-4.8
cvs diff: Diffing htdocs/gcc-4.9
cvs diff: Diffing htdocs/gcc-5
cvs diff: Diffing htdocs/gcc-6
cvs diff: Diffing htdocs/gcc-7
cvs diff: Diffing htdocs/gcc-8
Index: htdocs/gcc-8/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/porting_to.html,v
retrieving revision 1.1
diff -u -r1.1 porting_to.html
--- htdocs/gcc-8/porting_to.html 4 Mar 2017 14:21:41 -0000 1.1
+++ htdocs/gcc-8/porting_to.html 9 Mar 2017 10:49:34 -0000
@@ -31,6 +31,17 @@
<h2 id="cxx">C++ language issues</h2>
+<h2 id="mingw">MinGW issues</h2>
+
+<p>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. Prior versions of GCC would follow the
+configuration of MinGW runtime. This behavior can still be obtained by not
+using the above options or by using
+<code>--enable-mingw-wildcard=platform</code>.</p>
+
+
<h2 id="links">Links</h2>
</body>
cvs diff: Diffing htdocs/git
cvs diff: Diffing htdocs/img
cvs diff: Diffing htdocs/install
cvs diff: Diffing htdocs/java
cvs diff: Diffing htdocs/libstdc++
cvs diff: Diffing htdocs/news
cvs diff: Diffing htdocs/onlinedocs
cvs diff: Diffing htdocs/onlinedocs/4.6.0
cvs diff: Diffing htdocs/onlinedocs/4.6.1
cvs diff: Diffing htdocs/onlinedocs/4.6.2
cvs diff: Diffing htdocs/onlinedocs/4.6.3
cvs diff: Diffing htdocs/onlinedocs/4.6.4
cvs diff: Diffing htdocs/onlinedocs/4.7.0
cvs diff: Diffing htdocs/onlinedocs/4.7.1
cvs diff: Diffing htdocs/onlinedocs/4.7.2
cvs diff: Diffing htdocs/onlinedocs/4.7.3
cvs diff: Diffing htdocs/onlinedocs/4.7.4
cvs diff: Diffing htdocs/onlinedocs/4.8.0
cvs diff: Diffing htdocs/onlinedocs/4.8.1
cvs diff: Diffing htdocs/onlinedocs/4.8.2
cvs diff: Diffing htdocs/onlinedocs/4.8.3
cvs diff: Diffing htdocs/onlinedocs/4.8.4
cvs diff: Diffing htdocs/onlinedocs/4.8.5
cvs diff: Diffing htdocs/onlinedocs/4.9.0
cvs diff: Diffing htdocs/onlinedocs/4.9.1
cvs diff: Diffing htdocs/onlinedocs/4.9.2
cvs diff: Diffing htdocs/onlinedocs/4.9.3
cvs diff: Diffing htdocs/onlinedocs/4.9.4
cvs diff: Diffing htdocs/onlinedocs/5.1.0
cvs diff: Diffing htdocs/onlinedocs/5.2.0
cvs diff: Diffing htdocs/onlinedocs/5.3.0
cvs diff: Diffing htdocs/onlinedocs/5.4.0
cvs diff: Diffing htdocs/onlinedocs/6.1.0
cvs diff: Diffing htdocs/onlinedocs/6.2.0
cvs diff: Diffing htdocs/onlinedocs/6.3.0
cvs diff: Diffing htdocs/projects
cvs diff: Diffing htdocs/projects/bp
cvs diff: Diffing htdocs/projects/cxx-reflection
cvs diff: Diffing htdocs/projects/gomp
cvs diff: Diffing htdocs/projects/lto
cvs diff: Diffing htdocs/projects/strees
cvs diff: Diffing htdocs/projects/tree-ssa
cvs diff: Diffing htdocs/testing
next prev parent reply other threads:[~2017-03-09 10:51 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 ` Thomas Preudhomme [this message]
2017-03-09 10:59 ` [wwwdocs] gcc-8/porting_to.html 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
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=20845b34-f951-f2d1-0365-b8c8e788be5b@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).