Hi all,
I noticed when reading the documentation that BREAK_FROM_IMM_USE_SAFE
was removed at some point in 2006 and replaced with BREAK_FROM_IMM_USE_STMT.
2019-10-10 Joel Hutton joel.hut...@arm.com
* doc/tree-ssa.texi: Update renamed macro name.
From a9569599ee885842eabc6cc22e718486ceb7034d Mon Sep 17 00:00:00 2001
From: Joel Hutton
Date: Thu, 10 Oct 2019 11:12:17 +0100
Subject: [PATCH] Doc: FOR_EACH_IMM_USE_SAFE removed
---
gcc/doc/tree-ssa.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi
index 9714c5addfaad5d8418e88ded309a713439184b0..a7da6f9ef04264465d06cc55eded4a810642eaa5 100644
--- a/gcc/doc/tree-ssa.texi
+++ b/gcc/doc/tree-ssa.texi
@@ -385,14 +385,14 @@ optimization can manipulate the stmt when all the uses have been
processed. This is a little slower than the FAST version since it adds a
placeholder element and must sort through the list a bit for each statement.
This placeholder element must be also be removed if the loop is
-terminated early. The macro @code{BREAK_FROM_IMM_USE_SAFE} is provided
+terminated early. The macro @code{BREAK_FROM_IMM_USE_STMT} is provided
to do this :
@smallexample
FOR_EACH_IMM_USE_STMT (stmt, iterator, ssa_var)
@{
if (stmt == last_stmt)
-BREAK_FROM_SAFE_IMM_USE (iter);
+BREAK_FROM_IMM_USE_STMT (iter);
FOR_EACH_IMM_USE_ON_STMT (imm_use_p, iterator)
SET_USE (imm_use_p, ssa_var_2);
--
2.17.1
