https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106526
--- Comment #3 from Lars Wrenger ---
The array-bounds warning itself is nice. In most cases, it is good if the
compiler can find invalid memory accesses.
However, the wording of the warning is confusing. Strictly speaking, we are not
accessing a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106526
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106526
--- Comment #1 from Lars Wrenger ---
Same on C++: https://godbolt.org/z/7do3zhavf
