public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-4252] Fix comment typos noticed by Bernhard Date: Tue, 22 Nov 2022 23:23:20 +0000 (GMT) [thread overview] Message-ID: <20221122232320.EEBCE3854557@sourceware.org> (raw) https://gcc.gnu.org/g:a03b35a28db262546415e8f16829cbb027a75025 commit r13-4252-ga03b35a28db262546415e8f16829cbb027a75025 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: --- gcc/tree-ssa-dom.cc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) 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;
reply other threads:[~2022-11-22 23:23 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=20221122232320.EEBCE3854557@sourceware.org \ --to=law@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).