https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104655
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
CC| |msebor at gcc dot gnu.org
Status|WAITING |RESOLVED
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning in the test case in comment #6 is intentional: it triggers because
the hardcoded address (0xfee00000) doesn't refer to a known object, same as in
the test case in bug 99578 comment 0. The bug is still open because there's a
lack of consensus as to whether or how GCC should be enhanced to accept such
code without a warning. -Warray-bounds and -Wstringop-overflow/-overread
depend on optimizations some of which tend to expose new instances of warnings
as optimizers improve from one release to another.
*** This bug has been marked as a duplicate of bug 99578 ***
