Date:	Tue, 6 Oct 1998 21:52:03 -0400 (EDT)
Message-Id:	<199810070152.VAA04591@indy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:	<361AC3D2.1D94@cam.org> (message from Vic on Tue, 06 Oct 1998
	21:28:50 -0400)
Subject:	Re: Another silly question!
Reply-To:	djgpp AT delorie DOT com

> I think you get the highest level of warnings by using -Wall -O -ansi
> -pedantic

Even -Wall doesn't turn on *all* the warnings.  There are a few more
that are non-obviously warnings (i.e. the code may be correct, but gcc
can't tell for sure) that have to be explicitly enabled.  DJGPP's libc
makefiles do this.

Also be warned that using -ansi with DJGPP disables parts of the
system headers, so that the mere use of a non-ANSI function (including
POSIX functions) produces a warning.

Also, -Werror allows you to turn warnings into errors, so that
compilations fail unless they are warning-free.  DJGPP's libc does
this.

For reference, here are the command-line options DJGPP's libc is build
with:

-MD -O2 -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2
-malign-functions=2 -Wall -Wbad-function-cast -Wcast-qual -Werror
-Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wshadow
-Wstrict-prototypes -Wtraditional -Wwrite-strings -nostdinc

- Raw text -