This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH/fortran] Add option to make 1st error fatal

From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
To: Daniel Berlin <dberlin at dberlin dot org>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Sun, 30 Oct 2005 20:43:48 -0800
Subject: Re: [PATCH/fortran] Add option to make 1st error fatal
References: <20051031040500.GA22708@troutmask.apl.washington.edu> <200510310417.j9V4HU9X012721@earth.phy.uc.edu> <20051031042600.GA22982@troutmask.apl.washington.edu> <1130733305.8960.144.camel@linux.site>

On Sun, Oct 30, 2005 at 11:35:05PM -0500, Daniel Berlin wrote:
> 
> That just means your error recovery sucks :)

Grab the fortran code in PR 23538.
Run it through gfortran and enjoy.

> Normally, things just put error_mark_node in the appropriate place and
> move on until something checks error count.

gfortran frontend doesn't use the generic gcc error code.

No, I'm not going to rewrite gfortran's error/warning code
to use gcc's generic code.

-- 
Steve

Follow-Ups:
- Re: [PATCH/fortran] Add option to make 1st error fatal
  - From: Daniel Berlin

References:
- Re: [PATCH/fortran] Add option to make 1st error fatal
  - From: Steve Kargl
- Re: [PATCH/fortran] Add option to make 1st error fatal
  - From: Andrew Pinski
- Re: [PATCH/fortran] Add option to make 1st error fatal
  - From: Steve Kargl
- Re: [PATCH/fortran] Add option to make 1st error fatal
  - From: Daniel Berlin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]