This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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] fix PR 44782, implement -fmax-errors as a common option

From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: Nathan Froyd <froydnj at codesourcery dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
Date: Thu, 11 Nov 2010 15:24:46 -0600
Subject: Re: [PATCH] fix PR 44782, implement -fmax-errors as a common option
References: <20101109141929.GB7991@nightcrawler> <Pine.LNX.4.64.1011091525450.981@digraph.polyomino.org.uk> <20101109164437.GE7991@nightcrawler> <20101111211621.GA80377@troutmask.apl.washington.edu>

On Thu, Nov 11, 2010 at 3:16 PM, Steve Kargl
<sgk@troutmask.apl.washington.edu> wrote:
> On Tue, Nov 09, 2010 at 11:44:38AM -0500, Nathan Froyd wrote:
>>
>> gcc/fortran/
>> ? ? ? PR c/44782
>> ? ? ? * options.c (gfc_post_options): Initialize gfc_option.max_errors.
>> ? ? ? (gfc_handle_option) [OPT_fmax_errors_]: Remove.
>> ? ? ? * lang.opt (fmax-errors=): Remove.
>
> This part looks ok to me. ?I can't approve the other parts of
> the patch. ?Note, I have no opinion of the -ferror-limit vs
> -fmax-errors issue. ?Of course, I chose the name -fmax-errors. :)


The path is OK.

References:
- [PATCH] fix PR 44782, implement -fmax-errors for C-family languages
  - From: Nathan Froyd
- Re: [PATCH] fix PR 44782, implement -fmax-errors for C-family languages
  - From: Joseph S. Myers
- Re: [PATCH] fix PR 44782, implement -fmax-errors as a common option
  - From: Nathan Froyd
- Re: [PATCH] fix PR 44782, implement -fmax-errors as a common option
  - From: Steve Kargl

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