aboutsummaryrefslogtreecommitdiff
path: root/gcc/rust/backend/rust-compile-expr.cc
diff options
context:
space:
mode:
authorRichard Biener <rguenther@suse.de>2025-04-29 15:08:52 +0200
committerRichard Biener <rguenth@gcc.gnu.org>2025-04-30 14:52:47 +0200
commit5f44fcdfe18e72f2900d2757375843e88d32c535 (patch)
treefdf45e88c020a716dfec5dc730467691cbe92281 /gcc/rust/backend/rust-compile-expr.cc
parente12b09a67e41f470ea6ec5ad93c76ad44f0d28d5 (diff)
downloadgcc-5f44fcdfe18e72f2900d2757375843e88d32c535.zip
gcc-5f44fcdfe18e72f2900d2757375843e88d32c535.tar.gz
gcc-5f44fcdfe18e72f2900d2757375843e88d32c535.tar.bz2
tree-optimization/119960 - add validity checking to SLP scheduling
The following adds checks that when we search for a vector stmt insert location we arrive at one where all required operand defs are dominating the insert location. At the moment any such failure only blows up during SSA verification. There's the long-standing issue that we do not verify there exists a valid schedule of the SLP graph from BB vectorization into the existing CFG. We do not have the ability to insert vector stmts on the dominance frontier "end", nor to insert LC PHIs that would be eventually required. This should be done all differently, computing the schedule during analysis and failing if we can't schedule. PR tree-optimization/119960 * tree-vect-slp.cc (vect_schedule_slp_node): Sanity check dominance check on operand defs.
Diffstat (limited to 'gcc/rust/backend/rust-compile-expr.cc')
0 files changed, 0 insertions, 0 deletions