[committed] docs: Fix outdated reference to LOOPS_HAVE_MARKED_SINGLE_EXITS

Message ID YuFKY0JKfl4WyQdt@e124511.cambridge.arm.com
State Committed
Commit 5eb9f117a361538834b9740d59219911680717d1
Headers
Series [committed] docs: Fix outdated reference to LOOPS_HAVE_MARKED_SINGLE_EXITS |

Commit Message

Andrew Carlotti July 27, 2022, 2:23 p.m. UTC
  This reference has been wrong since 2007; committed as an obvious fix.

gcc/ChangeLog:

 * doc/loop.texi: Refer to LOOPS_HAVE_RECORDED_EXITS instead.
  

Patch

diff --git a/gcc/doc/loop.texi b/gcc/doc/loop.texi
index d7b71a24dbfed284b13da702bd5037691a515535..6e8657a074d2447db7ae9b75cbfbb71282b84287 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