From c048d56d7e1750c411ffc7f67415beab926c1d05 Mon Sep 17 00:00:00 2001 From: Kazu Hirata Date: Sat, 20 Mar 2004 14:03:34 +0000 Subject: class.c, [...]: Fix comment typos. * class.c, gjavah.c, lang.c: Fix comment typos. * gcj.texi: Fix typos. From-SVN: r79744 --- gcc/java/gcj.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gcc/java/gcj.texi') diff --git a/gcc/java/gcj.texi b/gcc/java/gcj.texi index 26edf69..a42e203 100644 --- a/gcc/java/gcj.texi +++ b/gcc/java/gcj.texi @@ -435,7 +435,7 @@ 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 +generation for all classes, unless overridden 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. @@ -443,7 +443,7 @@ 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. +or when not optimizing, and disabled when generating optimized binaries. @item --enable-assertions[=@var{class-or-package}] Generates code to check assertions. The option is perhaps misnamed, -- cgit v1.1