Re: [PATCH] add gcc_assert

[Nathan Sidwell <nathan at codesourcery dot com>]

Geoff Keating wrote:
>

> Yes, like that; except that it needs a documentation change somewhere, 
> probably install.texi.  OK with documentation.
here's the doc diff. installed.

nathan
--
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

Index: doc/install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.314
diff -c -3 -p -r1.314 install.texi
*** doc/install.texi	4 Sep 2004 00:15:42 -0000	1.314
--- doc/install.texi	7 Sep 2004 08:09:06 -0000
*************** compiler and may only work properly if y
*** 1099,1115 ****
  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.
  
  @item --enable-coverage
  @itemx --enable-coverage=@var{level}
--- 1099,1119 ----
  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{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}