Hi!
-fsanitize=bounds is one of the -fsanitize=undefined suboptions, therefore
it should be documented as such.
Fixed thusly, committed to trunk as obvious.
2014-06-30 Jakub Jelinek <ja...@redhat.com>
* doc/invoke.texi (-fsanitize=bounds): Move to the table with
-fsanitize=undefined suboptions.
--- gcc/doc/invoke.texi.jj 2014-06-30 09:28:48.000000000 +0200
+++ gcc/doc/invoke.texi 2014-06-30 14:18:01.203027487 +0200
@@ -5440,6 +5440,13 @@ signed char a = SCHAR_MAX;
a++;
@end smallexample
+@item -fsanitize=bounds
+@opindex fsanitize=bounds
+
+This option enables instrumentation of array bounds. Various out of bounds
+accesses are detected. Flexible array members are not instrumented, as well
+as initializers of variables with static storage.
+
@end table
While @option{-ftrapv} causes traps for signed overflows to be emitted,
@@ -5461,13 +5468,6 @@ This option enables floating-point type
We check that the result of the conversion does not overflow.
This option does not work well with @code{FE_INVALID} exceptions enabled.
-@item -fsanitize=bounds
-@opindex fsanitize=bounds
-
-This option enables instrumentation of array bounds. Various out of bounds
-accesses are detected. Flexible array members are not instrumented, as well
-as initializers of variables with static storage.
-
@item -fsanitize-recover
@opindex fsanitize-recover
By default @option{-fsanitize=undefined} sanitization (and its suboptions
Jakub
