diff options
| author | Richard Biener <rguenther@suse.de> | 2022-04-08 13:13:29 +0200 |
|---|---|---|
| committer | Richard Biener <rguenther@suse.de> | 2022-04-08 14:18:31 +0200 |
| commit | e5453bcc217ea4ac53a4ac277661d6ef0ccd425b (patch) | |
| tree | 456c81a41536808736967a76f8de280ca0fb1589 /gcc/config.gcc | |
| parent | 04ecadbeae51ac56f1a104b4858b6463b24dfaa2 (diff) | |
| download | gcc-e5453bcc217ea4ac53a4ac277661d6ef0ccd425b.zip gcc-e5453bcc217ea4ac53a4ac277661d6ef0ccd425b.tar.gz gcc-e5453bcc217ea4ac53a4ac277661d6ef0ccd425b.tar.bz2 | |
tree-optimization/105198 - wrong code with predictive commoning
When predictive commoning looks for a looparound PHI it tries
to match the entry value definition (a load) up with the appropriate
member of the chain. But it fails to consider stmts clobbering
the very same memory location inbetween the load and loop entry.
In theory we could be more clever on must aliases that would be
also picked up from a load (so not exactly stmt_kills_ref_p) and
use the stored value from that if it is an exact match. But we
currently have no way to propagate this information inside predcom.
2022-04-08 Richard Biener <rguenther@suse.de>
PR tree-optimization/105198
* tree-predcom.cc (find_looparound_phi): Check whether
the found memory location of the entry value is clobbered
inbetween the value we want to use and loop entry.
* gcc.dg/torture/pr105198.c: New testcase.
Diffstat (limited to 'gcc/config.gcc')
0 files changed, 0 insertions, 0 deletions