https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113551
Mikael Pettersson <mikpelinux at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpelinux at gmail dot com
--- Comment #20 from Mikael Pettersson <mikpelinux at gmail dot com> ---
For gcc-14 this test case was fixed by
dc48d1d1d4458773f89f21b2f019f66ddf88f2e5 is the first new commit
commit dc48d1d1d4458773f89f21b2f019f66ddf88f2e5
Author: Andrew MacLeod <amacl...@redhat.com>
Date: Thu Aug 17 11:13:14 2023 -0400
Fix range-ops operator_addr.
Lack of symbolic information prevents op1_range from beig able to draw
the same conclusions as fold_range can.
PR tree-optimization/111009
gcc/
* range-op.cc (operator_addr_expr::op1_range): Be more restrictive.
That commit was backported to gcc-13 in
421311a31a12b96143eb901fde0e020771fe71d4, and that fixed this test case there
too.
Not sure if this is the proper fix or just makes the issue latent.
