From: Jonny Grant <jg@jguk.org>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] correct function attribute typo
Date: Thu, 16 Mar 2023 22:37:41 +0000 [thread overview]
Message-ID: <640effa5-e1d6-94fe-cb8f-978d8a94f931@jguk.org> (raw)
Hello
There's a typo in the common function attribute docs, "nonnul" which this patch corrects.
https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#Common-Function-Attributes
gcc/ChangeLog
2023-03-16 Jonny Grant <jg@jguk.org>
* doc/extend.texi: correct function attribute typo
---
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 e0c5357291b..91dfdef4461 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -3657,7 +3657,7 @@ marked with nonnull is compared with null, and
@option{-Wnonnull-compare} option is enabled, a warning is issued.
@xref{Warning Options}.
@item The compiler may also perform optimizations based on the
-knowledge that @code{nonnul} parameters cannot be null. This can
+knowledge that @code{nonnull} parameters cannot be null. This can
currently not be disabled other than by removing the nonnull
attribute.
@end itemize
next reply other threads:[~2023-03-16 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 22:37 Jonny Grant [this message]
2023-03-19 1:30 ` Sandra Loosemore
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=640effa5-e1d6-94fe-cb8f-978d8a94f931@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).