* configure.ac (enable-checking): Add release option. Reorganize

	to avoid repetition.
	* configure: Rebuilt.
	* doc/install.texi (enable-checking): Amend documentation.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@87139 138bc75d-0d04-0410-961f-82ee72b054a4

1 files changed, 15 insertions, 11 deletions

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 7a2d3e59266..dfad815d49a 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -1099,17 +1099,21 @@ compiler and may only work properly if you are building the compiler
 with GCC@.  This is on by default when building from CVS or snapshots,
 but off for releases.  More control over the checks may be had by
 specifying @var{list}; the categories of checks available are
-@samp{assert}, @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl},
-@samp{rtlflag}, @samp{fold}, @samp{gcac} and @samp{valgrind}.  The check
-@samp{valgrind} requires the external @command{valgrind} simulator,
-available from @uref{http://valgrind.kde.org/}.  The default when
-@var{list} is not specified is @samp{assert,misc,tree,gc,rtlflag}; the
-checks @samp{rtl}, @samp{gcac} and @samp{valgrind} are very expensive.
-When checking is neither explicitly enabled nor disabled, assertion
-checks are still done.  To disable all checking,
-@samp{--disable-checking} must be explicitly requested.  Disabling
-assertions will make the compiler slightly faster but increase the risk
-undetected internal errors causing wrong code to be generated.
+@samp{release}, @samp{assert}, @samp{misc}, @samp{tree}, @samp{gc},
+@samp{rtl}, @samp{rtlflag}, @samp{fold}, @samp{gcac} and
+@samp{valgrind}.  The @samp{release} category enables only those checks
+suitable for release builds, currently this is just @samp{assert}.  The
+check @samp{valgrind} requires the external @command{valgrind}
+simulator, available from @uref{http://valgrind.kde.org/}.  The checks
+@samp{rtl}, @samp{gcac} and @samp{valgrind} are very expensive.  The
+default when @var{list} is not specified is
+@samp{assert,misc,tree,gc,rtlflag}.  That is also the default for
+development builds, when @samp{--enable-checking} is not specified.  For
+release builds the default, when @samp{--enable-checking} is not given,
+is @samp{release}.  To disable all checking, @samp{--disable-checking}
+must be explicitly requested.  Disabling assertions will make the
+compiler slightly faster but increase the risk of undetected internal
+errors causing wrong code to be generated.
 
 @item --enable-coverage
 @itemx --enable-coverage=@var{level}