From: Jonny Grant <jg@jguk.org>
To: gcc-patches@gcc.gnu.org
Subject: [PATCHJ]: Bugzilla 88860 - Clarify online manual infelicities
Date: Mon, 26 Dec 2022 21:00:05 +0000 [thread overview]
Message-ID: <f3166f68-a988-7476-bc71-7f3eb6d20deb@jguk.org> (raw)
2022-12-26 Jonathan Grant <jg@jguk.org>
* gcc/doc/extend.texi: Bugzilla 88860 - Clarify online manual infelicities
From 8b142ad8973dc67289e197e30966490a944e4819 Mon Sep 17 00:00:00 2001
From: Jonathan Grant <jg@jguk.org>
Date: Mon, 26 Dec 2022 20:58:29 +0000
Subject: [PATCH] Bugzilla 88860 - Clarify gcc online manual infelicities
Signed-off-by: Jonathan Grant <jg@jguk.org>
---
gcc/doc/extend.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index adba057c190..88fc625050b 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -9190,7 +9190,7 @@ have to optimize it to just @code{return 42 + 42;}.
This section describes the syntax with which @code{__attribute__} may be
used, and the constructs to which attribute specifiers bind, for the C
language. Some details may vary for C++ and Objective-C@. Because of
-infelicities in the grammar for attributes, some forms described here
+limitations in the grammar for attributes, some forms described here
may not be successfully parsed in all cases.
There are some problems with the semantics of attributes in C++. For
--
2.37.2
next reply other threads:[~2022-12-26 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 21:00 Jonny Grant [this message]
2023-03-01 12:54 ` Fwd: " Jonny Grant
2023-03-11 16:37 ` Jeff Law
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=f3166f68-a988-7476-bc71-7f3eb6d20deb@jguk.org \
--to=jg@jguk.org \
--cc=gcc-patches@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).