diff mbox

[wwwdocs] gcc-8/porting_to.html

Message ID 20845b34-f951-f2d1-0365-b8c8e788be5b@foss.arm.com
State New
Headers show

Commit Message

Thomas Preudhomme March 9, 2017, 10:51 a.m. UTC 
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>
>

Comments

Jakub Jelinek March 9, 2017, 10:58 a.m. UTC | #1 
On Thu, Mar 09, 2017 at 10:51:27AM +0000, Thomas Preudhomme wrote:
> Thanks Gerald,
> 
> JonY: what about the attached patch to document the change of behavior of
> GCC on Windows depending on the configure option used?

GCC 7 has not branched yet, so the change can't be committed anywhere.
It seems documenting something before it is actually changed is just too
weird.

	Jakub
Thomas Preudhomme March 9, 2017, 11:22 a.m. UTC | #2 
Hi Jakub,

I forgot to mention "ok for stage1?", my bad. JonY said he was queuing the 
corresponding changes in GCC for stage1 so I was just trying to have a complete 
story. I do not expect to commit this before the actual code change is committed.

Best regards,

Thomas

On 09/03/17 10:58, Jakub Jelinek wrote:
> On Thu, Mar 09, 2017 at 10:51:27AM +0000, Thomas Preudhomme wrote:
>> Thanks Gerald,
>>
>> JonY: what about the attached patch to document the change of behavior of
>> GCC on Windows depending on the configure option used?
>
> GCC 7 has not branched yet, so the change can't be committed anywhere.
> It seems documenting something before it is actually changed is just too
> weird.
>
> 	Jakub
>
Jonathan Yong March 9, 2017, 1:15 p.m. UTC | #3 
On 03/09/2017 11:22 AM, Thomas Preudhomme wrote:
> Hi Jakub,
> 
> I forgot to mention "ok for stage1?", my bad. JonY said he was queuing
> the corresponding changes in GCC for stage1 so I was just trying to have
> a complete story. I do not expect to commit this before the actual code
> change is committed.
> 

Right, I was waiting for GCC 8 to open.
Gerald Pfeifer March 12, 2017, 2:07 p.m. UTC | #4 
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?

+<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

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
+<code>--enable-mingw-wildcard=platform</code>.</p>

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
Jonathan Yong March 12, 2017, 11:51 p.m. UTC | #5 
On 03/12/2017 02:07 PM, Gerald Pfeifer wrote:
> 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?
> 
> +<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
> 
> 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
> +<code>--enable-mingw-wildcard=platform</code>.</p>
> 
> 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
> 

It should be part of the release notes since it only affects GCC itself,
not the actual generated output.
diff mbox

Patch

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