aboutsummaryrefslogtreecommitdiff
path: root/gcc/cp/lambda.cc
diff options
context:
space:
mode:
authorRichard Biener <rguenther@suse.de>2022-05-09 11:33:44 +0200
committerRichard Biener <rguenther@suse.de>2022-05-09 13:42:36 +0200
commitfaabc751d0bb7e7fe86abfe8991b0307d585874a (patch)
treecc97e4343aa2d8b777866139a6854a2f0ab9d306 /gcc/cp/lambda.cc
parent93416de0cb72358b95a96fa4341b7b93a6805842 (diff)
downloadgcc-faabc751d0bb7e7fe86abfe8991b0307d585874a.zip
gcc-faabc751d0bb7e7fe86abfe8991b0307d585874a.tar.gz
gcc-faabc751d0bb7e7fe86abfe8991b0307d585874a.tar.bz2
tree-optimization/105517 - avoid offset truncation during VN
When value-numbering an address expression like &p_74(D)->a1x[4294967295].a1; we are accumulating the byte offset in an 64bit integer. When later exploiting the duality between that and a POINTER_PLUS_EXPR we should avoid truncating that offset to fit in the target specific sizetype. While such overflows are generally undefined behavior, exploiting this may leads to spurious missing diagnostics. 2022-05-09 Richard Biener <rguenther@suse.de> PR tree-optimization/105517 * tree-ssa-sccvn.cc (vn_reference_lookup): Make sure the accumulated offset can be represented in the POINTER_PLUS_EXPR IL. (vn_reference_insert): Likewise. * poly-int.h (sext_hwi): Add poly version of sext_hwi.
Diffstat (limited to 'gcc/cp/lambda.cc')
0 files changed, 0 insertions, 0 deletions