]> git.ipfire.org Git - thirdparty/gcc.git/commit
projects / thirdparty / gcc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 95f1097) | patch
middle-end/119706 - allow POLY_INT_CST as is_gimple_mem_ref_addr
authorRichard Biener <rguenther@suse.de>
Thu, 10 Apr 2025 11:30:42 +0000 (13:30 +0200)
committerRichard Biener <rguenth@gcc.gnu.org>
Thu, 10 Apr 2025 12:34:29 +0000 (14:34 +0200)
commitbf812c6ad83ec0b241bb3fecc7e68f883b6083df
treef10a5057f8a8a4a7f802f4a6901d4a15e75a2632tree | snapshot
parent95f10974a9190e345776604480a2df0191104308commit | diff
middle-end/119706 - allow POLY_INT_CST as is_gimple_mem_ref_addr

We currently only INTEGER_CST, but not POLY_INT_CST, which leads
to the situation that when the POLY_INT_CST is only indrectly
present via a SSA def the IL is valid but when propagated it's not.
That's unsustainable.

PR middle-end/119706
* gimple-expr.cc (is_gimple_mem_ref_addr): Also allow
POLY_INT_CST.
gcc/gimple-expr.cc diff | blob | blame | history
Mirror of https://gcc.gnu.org/git/gcc.git