This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH/fortran] Add option to make 1st error fatal
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: sgk at troutmask dot apl dot washington dot edu (Steve Kargl)
- Cc: pinskia at physics dot uc dot edu (Andrew Pinski), fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Sun, 30 Oct 2005 23:29:45 -0500 (EST)
- Subject: 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.
I am trying to say that the behavior with -Werror on gcc,
is that it turns warnings into errors and does not make
them a fatal error.
-- Pinski