This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
[PATCH]: Activate $(STRICT_WARN) for fortran subdir
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- To: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Thu, 10 Mar 2005 10:25:57 -0500 (EST)
- Subject: [PATCH]: Activate $(STRICT_WARN) for fortran subdir
The fortran subdirectory currently uses the "loose" set of warning
flags so it's missing a bunch, and it also doesn't utilize -Werror to
automatically keep things clean.
This patch activates the "strict" set as per the way all the other
frontends do. I added -Wno-error because there are some warnings and
I don't want to hose bootstrap. I'll post fixes in a followup patch
and remove -Wno-error when it's safe to do so.
Bootstrapped on x86_64-unknown-linux-gnu with --enable-languages=f95
Ok for mainline?
Thanks,
--Kaveh
2005-03-10 Kaveh R. Ghazi <ghazi@caip.rutgers.edu>
* Make-lang.in (fortran-warn): Set to $(STRICT_WARN) -Wno-error.
diff -rup orig/egcc-CVS20050223/gcc/fortran/Make-lang.in egcc-CVS20050223/gcc/fortran/Make-lang.in
--- orig/egcc-CVS20050223/gcc/fortran/Make-lang.in 2004-11-13 02:35:54.000000000 -0500
+++ egcc-CVS20050223/gcc/fortran/Make-lang.in 2005-02-24 17:35:24.074858872 -0500
@@ -48,14 +48,8 @@ GFORTRAN_CROSS_NAME := $(shell echo gfor
#^L
-# This is in addition to the warning flags defined by default.
-# You can use it to enable/disable warnings globally or for specific
-# files, e.g.
-# fortran-warn = -Wno-strict-prototypes
-# fortran/arith.o-warn = -Wno-error
-#
-# We don't need these cheats, everything builds fine with all warnings
-# enabled and -Werror.
+# Use strict warnings for this front end.
+fortran-warn = $(STRICT_WARN) -Wno-error
# These are the groups of object files we have. The F95_PARSER_OBJS are
# all the front end files, the F95_OBJS are the files for the translation