public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Carlotti <acarlotti@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1861] docs: Fix outdated reference to LOOPS_HAVE_MARKED_SINGLE_EXITS Date: Wed, 27 Jul 2022 14:22:30 +0000 (GMT) [thread overview] Message-ID: <20220727142230.579A33857B86@sourceware.org> (raw) https://gcc.gnu.org/g:5eb9f117a361538834b9740d59219911680717d1 commit r13-1861-g5eb9f117a361538834b9740d59219911680717d1 Author: Andrew Carlotti <andrew.carlotti@arm.com> Date: Wed Jul 27 15:11:51 2022 +0100 docs: Fix outdated reference to LOOPS_HAVE_MARKED_SINGLE_EXITS gcc/ChangeLog: * doc/loop.texi: Refer to LOOPS_HAVE_RECORDED_EXITS instead. Diff: --- gcc/doc/loop.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/doc/loop.texi b/gcc/doc/loop.texi index d7b71a24dbf..6e8657a074d 100644 --- a/gcc/doc/loop.texi +++ b/gcc/doc/loop.texi @@ -210,7 +210,7 @@ loop in depth-first search order in reversed CFG, ordered by dominance relation, and breath-first search order, respectively. @item @code{single_exit}: Returns the single exit edge of the loop, or @code{NULL} if the loop has more than one exit. You can only use this -function if LOOPS_HAVE_MARKED_SINGLE_EXITS property is used. +function if @code{LOOPS_HAVE_RECORDED_EXITS} is used. @item @code{get_loop_exit_edges}: Enumerates the exit edges of a loop. @item @code{just_once_each_iteration_p}: Returns true if the basic block is executed exactly once during each iteration of a loop (that is, it
reply other threads:[~2022-07-27 14:22 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=20220727142230.579A33857B86@sourceware.org \ --to=acarlotti@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).