This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [PATCH/fortran] Add option to make 1st error fatal
On Sun, Oct 30, 2005 at 11:17:30PM -0500, Andrew Pinski wrote:
> >
> > On Sun, Oct 30, 2005 at 10:55:00PM -0500, Andrew Pinski wrote:
> > > > Here's a new patch based on feedback from Andrew Pinski on IRC.
> > > > Bubblestrap and regression tested on i386-*-freebsd.
> > >
> > > -Werror does not do what option does. It just changes warnings
> > > to be considered an error for the return value.
> >
> > According to 'tkinfo gcc',
> >
> > `-Werror'
> > Make all warnings into hard errors. Source code which triggers
> > warnings will be rejected.
> >
> > This is exactly what my patch does. A warning becomes a fatal
> > error.
>
> No, it turns them into normal errors and not fatal errors.
I have not idea what you mean. If I use "gfortran -Werror"
with my patch, gfortran will exit when it hits the first
warning. That appears to be fairly fatal.
> > > And you really don't need to document these options as they are
> > > generic options.
> >
> > It's a PITA to get Fortran users to read a Fortran manual, I
> > suspect most would not read what would appear to be a C
> > compiler's manual.
>
> Well it is too late to change that, oh well. Maybe for
> 4.2, this should change.
Actually, there is a valid reason to document -Werror
in the gfortran manual. The current text strongly
discourageous a user from using -Werror with legacy code,
which can produce volumes of warnings.
--
Steve