[Bug tree-optimization/119399] Overlap check in vectorized code may invoke UB

2025-04-10 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119399 --- Comment #6 from GCC Commits --- The trunk branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:4c8c373495d7d863dfb7102726ac3b4b41685df4 commit r15-9355-g4c8c373495d7d863dfb7102726ac3b4b41685df4 Author: Richard Sandiford Da

[Bug tree-optimization/119399] Overlap check in vectorized code may invoke UB

2025-04-10 Thread rsandifo at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119399 --- Comment #5 from Richard Sandiford --- (In reply to rguent...@suse.de from comment #4) > >, so for a 4-element > > vector, the only problem cases are p==q+4, p==q+8 and p==q+12. That's > > equivalent to testing whether the unsigned value p-(

[Bug tree-optimization/119399] Overlap check in vectorized code may invoke UB

2025-04-09 Thread rguenther at suse dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119399 --- Comment #4 from rguenther at suse dot de --- On Wed, 9 Apr 2025, rsandifo at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119399 > > Richard Sandiford changed: > >What|Removed

[Bug tree-optimization/119399] Overlap check in vectorized code may invoke UB

2025-04-09 Thread rsandifo at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119399 Richard Sandiford changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassig

[Bug tree-optimization/119399] Overlap check in vectorized code may invoke UB

2025-03-21 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119399 Richard Biener changed: What|Removed |Added Last reconfirmed||2025-03-21 Keywords|

[Bug tree-optimization/119399] Overlap check in vectorized code may invoke UB

2025-03-21 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119399 --- Comment #2 from Richard Biener --- Note the possible UB is in the POINTER_DIFF_EXPR _25 = p_12(D) - _7 which we should arguably not use but instead use an integer type difference when different objects are involved. Still the actual alias c