This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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.
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |