[gfortran,committed] Don't use -Wno-error to build Fortran front-end files

[FX Coudert <fxcoudert at gmail dot com>]

fortran/Make-lang.in contained directives to use -Wno-error to build  
expr.o, resolve.o, simplify.o and trans-expr.o, because of warnings  
due to GMP headers. This warning has been taken care of in GMP  
headers since at least 4.1, which is the minimal required version for  
mainline nowadays. The use of -Wno-error is thus not needed anymore,  
and it's preventing real warnings to be seen during bootstrap (I  
remember at least two occurences of that in the recent months).

Committed to mainline after bootstrapping on i686-linux twice: once  
with the current GMP, and another time with GMP-4.1.



2007-05-19  Francois-Xavier Coudert  <fxcoudert@gcc.gnu.org>

	PR fortran/30820
	* Make-lang.in: Remove use of -Wno-error for expr.o, resolve.o,
	simplify.o and trans-common.o.


Index: Make-lang.in
===================================================================
--- Make-lang.in        (revision 124858)
+++ Make-lang.in        (working copy)
@@ -48,13 +48,6 @@ GFORTRAN_TARGET_INSTALL_NAME := $(target
# Use strict warnings for this front end.
fortran-warn = $(STRICT_WARN)
-# These files get warnings from an inline function in GMP saying:
-# "control may reach end of non-void function '__gmpz_get_ui' being  
inlined"
-fortran/expr.o-warn = -Wno-error
-fortran/resolve.o-warn = -Wno-error
-fortran/simplify.o-warn = -Wno-error
-fortran/trans-common.o-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
# from the parse tree to GENERIC