https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106526
--- Comment #3 from Lars Wrenger <wrenger at sra dot uni-hannover.de> --- 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 an array (even if *x == x[0]).
