[Bug c/84054] seems -fno-bounds-checking no longer supported

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84054

--- Comment #2 from Jonathan Wakely  ---
Firstly, GCC 4.8.1 has not been supported here for several years, and secondly
the option is clearly documented as not doing anything for C.


https://gcc.gnu.org/onlinedocs/gcc-4.8.1/gcc/Code-Gen-Options.html

-fbounds-check
For front ends that support it, generate additional code to check that
indices used to access arrays are within the declared range. This is
currently only supported by the Java and Fortran front ends, where this
option defaults to true and false respectively.



https://gcc.gnu.org/onlinedocs/gcc-3.4.5/gcc/Code-Gen-Options.html

-fbounds-check
For front-ends that support it, generate additional code to check that
indices used to access arrays are within the declared range. This is
currently only supported by the Java and Fortran 77 front-ends, where
this option defaults to true and false respectively.

[Bug c/84054] seems -fno-bounds-checking no longer supported

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84054

Richard Biener  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Richard Biener  ---
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.