diff options
| author | Nathan Sidwell <nathan@codesourcery.com> | 2005-03-24 14:09:06 +0000 |
|---|---|---|
| committer | Nathan Sidwell <nathan@gcc.gnu.org> | 2005-03-24 14:09:06 +0000 |
| commit | b53ef39560d2eed35fbeef8295687cac2eefabee (patch) | |
| tree | 28f4fcc6528302933788606c837a86d7af18eb57 /gcc/doc | |
| parent | 0a2198f5125444acabd8c7c0ef1afcd3842ae27c (diff) | |
| download | gcc-b53ef39560d2eed35fbeef8295687cac2eefabee.zip gcc-b53ef39560d2eed35fbeef8295687cac2eefabee.tar.gz gcc-b53ef39560d2eed35fbeef8295687cac2eefabee.tar.bz2 | |
configure.ac (enable-checking): Add 'runtime' option.
* configure.ac (enable-checking): Add 'runtime' option.
* doc/install.texi (enable-checking): Document 'runtime' checking.
* tsystem.h (gcc_assert, gcc_unreachable): Define.
* config.in: Regenerated.
* configure: Regenerated.
From-SVN: r96990
Diffstat (limited to 'gcc/doc')
| -rw-r--r-- | gcc/doc/install.texi | 27 |
1 files changed, 14 insertions, 13 deletions
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 0a629a7..471c5a0 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -1114,20 +1114,21 @@ 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{release}, @samp{assert}, @samp{misc}, @samp{tree}, @samp{gc}, -@samp{rtl}, @samp{rtlflag}, @samp{fold}, @samp{gcac} and +@samp{rtl}, @samp{rtlflag}, @samp{runtime}, @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. +suitable for release builds, currently this is @samp{assert} and +@samp{runtime}. 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,runtime}. 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 and runtime slightly faster +but increase the risk of undetected internal errors causing wrong code +to be generated. @item --enable-coverage @itemx --enable-coverage=@var{level} |