]> git.ipfire.org Git - thirdparty/gcc.git/commit
projects / thirdparty / gcc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 550edc9) | 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>
Tue, 24 Jun 2025 11:09:05 +0000 (13:09 +0200)
commit75f255c11f7e5a5099ad909606e21ec6bf9b82cc
treefd1745289ef9de8cbda555724d99a204c5c8acbatree
parent550edc99476376ee0350be90b9e61b337ffb0ff3commit | 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.

(cherry picked from commit bf812c6ad83ec0b241bb3fecc7e68f883b6083df)
gcc/gimple-expr.cc diff | blob | blame | history
Mirror of https://gcc.gnu.org/git/gcc.git