From: Jeff Law <jlaw@ventanamicro.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [committed] Fix comment typos noticed by Bernhard
Date: Tue, 22 Nov 2022 16:24:36 -0700 [thread overview]
Message-ID: <db876775-3e1b-172f-18e3-d593ef766832@ventanamicro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 86 bytes --]
Minor comment typo fixes as noticed by Bernhard.
Installed onto the trunk,
Jeff
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 1037 bytes --]
commit a03b35a28db262546415e8f16829cbb027a75025
Author: Jeff Law <jlaw@ventanamicro.com>
Date: Tue Nov 22 16:22:18 2022 -0700
Fix comment typos noticed by Bernhard
gcc/
* tree-ssa-dom.cc (record_edge_info): Fix comment typos.
diff --git a/gcc/tree-ssa-dom.cc b/gcc/tree-ssa-dom.cc
index c7f095d79fc..e82f4f73a66 100644
--- a/gcc/tree-ssa-dom.cc
+++ b/gcc/tree-ssa-dom.cc
@@ -673,10 +673,10 @@ record_edge_info (basic_block bb)
{
/* At this point we know the exit condition is loop
invariant. The only way to get out of the loop is
- if never traverses the backedge to begin with. This
- implies that any PHI nodes create equivalances we can
- attach to the loop exit edge. */
- int alternative
+ if it never traverses the backedge to begin with. This
+ implies that any PHI nodes create equivalances that we
+ can attach to the loop exit edge. */
+ int bool
= (EDGE_PRED (bb, 0)->flags & EDGE_DFS_BACK) ? 1 : 0;
gphi_iterator gsi;
next reply other threads:[~2022-11-22 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 23:24 Jeff Law [this message]
2022-11-22 23:28 ` Andrew Pinski
2022-11-22 23:32 ` Jeff Law
2022-11-22 23:38 ` 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=db876775-3e1b-172f-18e3-d593ef766832@ventanamicro.com \
--to=jlaw@ventanamicro.com \
--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).