public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108521] gcc/doc/invoke.texi contains remnants of Cygwin options removed in 2010-10-07
Date: Thu, 18 Jan 2024 19:41:13 +0000 [thread overview]
Message-ID: <bug-108521-4-8b6N90m4Xa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108521-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108521
--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sandra Loosemore <sandra@gcc.gnu.org>:
https://gcc.gnu.org/g:b6c4fcda7fea2c6e14f539780f976bdc1d2591fb
commit r14-8259-gb6c4fcda7fea2c6e14f539780f976bdc1d2591fb
Author: Brian Inglis <Brian.Inglis@Shaw.ca>
Date: Thu Jan 18 19:29:01 2024 +0000
Remove remnant of removed Cygwin options from invoke.texi [PR108521]
The -mcygwin option for x86 Windows was removed in 2010 by commit
3edeb30d044a4852881c34229e618b34f95b0d9e, but this reference was
overlooked.
gcc/ChangeLog
PR target/108521
* doc/invoke.texi (Option Summary): Remove -mcygwin and -mno-cygwin
from x86 Windows Options.
next prev parent reply other threads:[~2024-01-18 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 16:44 [Bug target/108521] New: doc/invoke.texi " Brian.Inglis at SystematicSw dot ab.ca
2023-01-24 16:47 ` [Bug target/108521] " Brian.Inglis at SystematicSw dot ab.ca
2023-01-24 20:37 ` [Bug target/108521] gcc/doc/invoke.texi " pinskia at gcc dot gnu.org
2023-01-24 20:39 ` pinskia at gcc dot gnu.org
2024-01-18 19:41 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-18 19:43 ` sandra at gcc dot gnu.org
2024-01-20 17:22 ` pinskia at gcc dot gnu.org
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=bug-108521-4-8b6N90m4Xa@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).