public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-2186] docs: add missing 'see' word Date: Fri, 9 Jul 2021 07:50:15 +0000 (GMT) [thread overview] Message-ID: <20210709075015.7C15A3853837@sourceware.org> (raw) https://gcc.gnu.org/g:b5405babd82b84a65efab4e59ffbf22c8c93ff53 commit r12-2186-gb5405babd82b84a65efab4e59ffbf22c8c93ff53 Author: Sergei Trofimovich <siarheit@google.com> Date: Fri Jul 9 08:19:37 2021 +0100 docs: add missing 'see' word gcc/ChangeLog: * doc/md.texi: Add missing 'see' word. Diff: --- gcc/doc/md.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi index cc92ebd26aa..7a4d24ead90 100644 --- a/gcc/doc/md.texi +++ b/gcc/doc/md.texi @@ -9937,7 +9937,7 @@ Lengths are measured in addressable storage units (bytes). Note that it is possible to call functions via the @code{symbol_ref} mechanism to compute the length of an insn. However, if you use this mechanism you must provide dummy clauses to express the maximum length -without using the function call. You can an example of this in the +without using the function call. You can see an example of this in the @code{pa} machine description for the @code{call_symref} pattern. The following macros can be used to refine the length computation:
reply other threads:[~2021-07-09 7:50 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=20210709075015.7C15A3853837@sourceware.org \ --to=slyfox@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).