public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-5923] docs: add missing @item for the first item Date: Mon, 13 Dec 2021 10:57:01 +0000 (GMT) [thread overview] Message-ID: <20211213105701.98906385840C@sourceware.org> (raw) https://gcc.gnu.org/g:3788c4ed2c774e36b2721ee2af454591a42afdeb commit r12-5923-g3788c4ed2c774e36b2721ee2af454591a42afdeb Author: Martin Liska <mliska@suse.cz> Date: Mon Dec 13 11:56:24 2021 +0100 docs: add missing @item for the first item gcc/ChangeLog: * doc/extend.texi: Use @item for the first @itemx entry. Diff: --- 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 266ef76e5c3..7869605bec2 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -2524,7 +2524,7 @@ The following attributes are supported on most targets. @table @code @c Keep this table alphabetized by attribute name. Treat _ as space. -@itemx access (@var{access-mode}, @var{ref-index}) +@item access (@var{access-mode}, @var{ref-index}) @itemx access (@var{access-mode}, @var{ref-index}, @var{size-index}) The @code{access} attribute enables the detection of invalid or unsafe
reply other threads:[~2021-12-13 10:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211213105701.98906385840C@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).