https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84054
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Huh. C code never (no longer?) supports something like "bounds checking".
There's a no-op option called -fbounds-check which only has an effect for
Fortran and Java.
It looks like the GCC 3.4 driver accepts random unknown options (ignoring
them), including -fbounds-checkignsakfdhi and the supported option
was -fbounds-check in the first place. -fbounds-checking never existed.
