First do add_noreturn_fake_exit_edges in connect_infinite_loops_to_exit
authorRichard Biener <rguenther@suse.de>
Thu, 25 Feb 2021 10:31:37 +0000 (11:31 +0100)
committerRichard Biener <rguenther@suse.de>
Fri, 23 Apr 2021 10:05:42 +0000 (12:05 +0200)
commit58ad6b2802592f1448eed48e8ad4e0e87985cecb
tree30b72ca9d3cf65ffb8a78916140aca0253359da6
parent500305a92ef85e6b87ad428a35221c62f4037b93
First do add_noreturn_fake_exit_edges in connect_infinite_loops_to_exit

Most callers of connect_infinite_loops_to_exit already do this but
the few that do not end up with extra exit edges.  The following
makes that consistent, also matching the post-dominance DFS walk code.

2021-02-25  Richard Biener  <rguenther@suse.de>

* cfganal.c (connect_infinite_loops_to_exit): First call
add_noreturn_fake_exit_edges.
* ipa-sra.c (process_scan_results): Do not call the now redundant
add_noreturn_fake_exit_edges.
* predict.c (tree_estimate_probability): Likewise.
(rebuild_frequencies): Likewise.
* store-motion.c (one_store_motion_pass): Likewise.
gcc/cfganal.c
gcc/ipa-sra.c
gcc/predict.c
gcc/store-motion.c