Re: PATCH for better assertion control.

[Per Bothner <per at bothner dot com>]

I checked this into mainline:
http://gcc.gnu.org/ml/java/2004-03/msg00150.html
http://gcc.gnu.org/ml/java/2004-03/msg00160.html

I also checked in the attached documentation.
--
	--Per Bothner
per@bothner.com   http://per.bothner.com/

2004-03-19  Per Bothner  <per@bothner.com>

	* gcj.texi (Code Generation):  Document new flags and assert defaults.

Index: gcj.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/java/gcj.texi,v
retrieving revision 1.58
diff -u -p -r1.58 gcj.texi
--- gcj.texi	17 Mar 2004 00:00:40 -0000	1.58
+++ gcj.texi	19 Mar 2004 23:31:17 -0000
@@ -431,6 +431,27 @@ to initialize static classes upon their 
 isn't carried out if @code{-C} was specified.) When compiling to native
 code, @code{-fno-optimize-static-class-initialization} will turn this
 optimization off, regardless of the optimization level in use.
+
+@item --disable-assertions[=@var{class-or-package}]
+Don't include code for checking assertions in the compiled code.
+If @code{=@var{class-or-package}} is missing disables assertion code
+generation for all classes, unless overrideen by a more
+specific @code{--enable-assertions} flag.
+If @var{class-or-package} is a class name, only disables generating
+assertion checks within the named class or its inner classes.
+If @var{class-or-package} is a package name, disables generating
+assertion checks within the named package or a subpackage.
+
+By default, assertions are enabled when generating class files
+or when not optimizaing, and disabled when generating optimized binaries.
+
+@item --enable-assertions[=@var{class-or-package}]
+Generates code to check assertions.  The option is perhaps misnamed,
+as you still need to turn on assertion checking at run-time,
+and we don't support any easy way to do that.
+So this flag isn't very useful yet, except to partially override
+@code{--disable-assertions}.
+
 @end table