aboutsummaryrefslogtreecommitdiff
path: root/gcc/diagnostic-format-json.cc
diff options
context:
space:
mode:
authorRichard Biener <rguenther@suse.de>2024-09-19 14:58:18 +0200
committerRichard Biener <rguenth@gcc.gnu.org>2024-09-19 16:26:28 +0200
commit5b5a36b122e1205449f1512bf39521b669e713ef (patch)
treed0e5392098ece9d8c7f47ba7bd8e2aba2959be97 /gcc/diagnostic-format-json.cc
parent77bd23a3e247555ba427d01af8e5713934be8d5b (diff)
downloadgcc-5b5a36b122e1205449f1512bf39521b669e713ef.zip
gcc-5b5a36b122e1205449f1512bf39521b669e713ef.tar.gz
gcc-5b5a36b122e1205449f1512bf39521b669e713ef.tar.bz2
tree-optimization/116768 - wrong dependence analysis
The following reverts a bogus fix done for PR101009 and instead makes sure we get into the same_access_functions () case when computing the distance vector for g[1] and g[1] where the constants ended up having different types. The generic code doesn't seem to handle loop invariant dependences. The special case gets us both ( 0 ) and ( 1 ) as distance vectors while formerly we got ( 1 ), which the PR101009 fix changed to ( 0 ) with bad effects on other cases as shown in this PR. PR tree-optimization/116768 * tree-data-ref.cc (build_classic_dist_vector_1): Revert PR101009 change. * tree-chrec.cc (eq_evolutions_p): Make sure (sizetype)1 and (int)1 compare equal. * gcc.dg/torture/pr116768.c: New testcase.
Diffstat (limited to 'gcc/diagnostic-format-json.cc')
0 files changed, 0 insertions, 0 deletions