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-6039] docs: Fix spelling issues in -fipa-strict-aliasing.
Date: Fri, 17 Dec 2021 13:34:56 +0000 (GMT)	[thread overview]
Message-ID: <20211217133456.639EE3858439@sourceware.org> (raw)

https://gcc.gnu.org/g:7fa2a204670d12961cb199490d11bb0fd685fc01

commit r12-6039-g7fa2a204670d12961cb199490d11bb0fd685fc01
Author: Martin Liska <mliska@suse.cz>
Date:   Fri Dec 17 14:33:35 2021 +0100

    docs: Fix spelling issues in -fipa-strict-aliasing.
    
    gcc/ChangeLog:
    
            * doc/invoke.texi: Fix spelling issues.

Diff:
---
 gcc/doc/invoke.texi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 37836a7d614..8f69e53e68e 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -12425,10 +12425,10 @@ The @option{-fstrict-aliasing} option is enabled at levels
 
 @item -fipa-strict-aliasing
 @opindex fipa-strict-aliasing
-Constrols whether rules of @option{-fstrict-aliasing} are applied across
+Controls whether rules of @option{-fstrict-aliasing} are applied across
 function boundaries.  Note that if multiple functions gets inlined into a
-signle function the memory accesses are no longer considred to be crossing a
-function bounday.
+single function the memory accesses are no longer considered to be crossing a
+function boundary.
 
 The @option{-fipa-strict-aliasing} option is enabled by default and is
 effective only in combination with @option{-fstrict-aliasing}.


                 reply	other threads:[~2021-12-17 13:34 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=20211217133456.639EE3858439@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: 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).