[committed] analyzer: "__analyzer_dump_state" has no side-effects

David Malcolm dmalcolm@redhat.com
Fri Nov 12 19:03:04 GMT 2021


Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as 72f1c1c452198ba1df6f70959180b201cedc506e.

gcc/analyzer/ChangeLog:
	* engine.cc (exploded_node::on_stmt_pre): Return when handling
	"__analyzer_dump_state".

Signed-off-by: David Malcolm <dmalcolm@redhat.com>
---
 gcc/analyzer/engine.cc | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/gcc/analyzer/engine.cc b/gcc/analyzer/engine.cc
index f21f8e5b78a..b29a21cce30 100644
--- a/gcc/analyzer/engine.cc
+++ b/gcc/analyzer/engine.cc
@@ -1325,8 +1325,11 @@ exploded_node::on_stmt_pre (exploded_graph &eg,
 	  return;
 	}
       else if (is_special_named_call_p (call, "__analyzer_dump_state", 2))
-	state->impl_call_analyzer_dump_state (call, eg.get_ext_state (),
-					      ctxt);
+	{
+	  state->impl_call_analyzer_dump_state (call, eg.get_ext_state (),
+						ctxt);
+	  return;
+	}
       else if (is_setjmp_call_p (call))
 	{
 	  state->m_region_model->on_setjmp (call, this, ctxt);
-- 
2.26.3



More information about the Gcc-patches mailing list