public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc(refs/users/pheeck/heads/sccp)] sccp fix: update_stmt now on the new stmt
@ 2023-02-28 11:51 Filip Kastl
0 siblings, 0 replies; only message in thread
From: Filip Kastl @ 2023-02-28 11:51 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:28f460430a0a902e751d63a7ad087bbf5cfa7ea3
commit 28f460430a0a902e751d63a7ad087bbf5cfa7ea3
Author: Filip Kastl <filip.kastl@gmail.com>
Date: Tue Feb 28 12:51:34 2023 +0100
sccp fix: update_stmt now on the new stmt
Diff:
---
gcc/sccp.cc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gcc/sccp.cc b/gcc/sccp.cc
index 33a8ac3795f..6c8791d8724 100644
--- a/gcc/sccp.cc
+++ b/gcc/sccp.cc
@@ -473,7 +473,7 @@ replace_use_by (tree get_replaced, tree replace_by, bitmap need_eh_cleanup,
cleanup_after_replace (use_stmt, gsi_stmt (gsi), need_eh_cleanup,
need_ab_cleanup, stmts_to_fixup,
false, false);
- update_stmt (use_stmt);
+ update_stmt (gsi_stmt (gsi));
}
}
@@ -640,6 +640,8 @@ sccp_propagate (auto_vec<gimple *> ©_stmts)
/* Remove data structs for cleanup after stmt modification. */
BITMAP_FREE (need_eh_cleanup);
BITMAP_FREE (need_ab_cleanup);
+ vec_free (stmts_to_fixup);
+
// TODO Should I free the vec? Or is it freed automatically?
/* We want to remove dead MEM PHIs because memory is in FUD SSA and the dead
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-02-28 11:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-28 11:51 [gcc(refs/users/pheeck/heads/sccp)] sccp fix: update_stmt now on the new stmt Filip Kastl
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).