diff options
| author | Richard Biener <rguenther@suse.de> | 2022-08-23 14:05:34 +0200 |
|---|---|---|
| committer | Richard Biener <rguenther@suse.de> | 2022-08-24 08:47:23 +0200 |
| commit | b6864f4ee87fb56299fc82e1e0ced127b747d87a (patch) | |
| tree | d48a187a5058d81a73ec4aa53301bfd213fff3fb /gcc/config/loongarch/loongarch.opt | |
| parent | 82d46ad79e79394f374bc0ddb7591d166b0b61eb (diff) | |
| download | gcc-b6864f4ee87fb56299fc82e1e0ced127b747d87a.zip gcc-b6864f4ee87fb56299fc82e1e0ced127b747d87a.tar.gz gcc-b6864f4ee87fb56299fc82e1e0ced127b747d87a.tar.bz2 | |
Speedup path discovery in predicate::use_cannot_happen
The following reverts a hunk from r8-5789-g11ef0b22d68cd1 that
made compute_control_dep_chain start from function entry rather
than the immediate dominator of the source block of the edge with
the undefined value on the PHI node. Reverting at that point
does not reveal any testsuite FAIL, in particular the added
testcase still passes. The following adjusts this to the other
function that computes predicates that hold on the PHI incoming
edges with undefined values, predicate::init_from_phi_def, which
starts at the immediate dominator of the PHI. That's much less
likely to run into the CFG walking limit.
* gimple-predicate-analysis.cc (predicate::use_cannot_happen):
Start the compute_control_dep_chain walk from the immediate
dominator of the PHI.
Diffstat (limited to 'gcc/config/loongarch/loongarch.opt')
0 files changed, 0 insertions, 0 deletions