On 10/14/16 12:17, David Malcolm wrote:
How about splitting out the bail-out code into a separate function:
diagnostic_handle_max_errors
Having discovered how fortran buffers errors, I think this approach is
necessary. I think I'm going to be in assignment-limbo for a little while though
On 10/15/16 05:31, Andreas Schwab wrote:
On Okt 13 2016, Nathan Sidwell wrote:
2016-10-13 Nathan Sidwell
* diagnostic.c (diagnostic_action_after_output): Remove max error
handling here
(diagnostic_report_diagnostic): ... do it here instead.
All tests that use
On Okt 13 2016, Nathan Sidwell wrote:
> 2016-10-13 Nathan Sidwell
>
> * diagnostic.c (diagnostic_action_after_output): Remove max error
> handling here
> (diagnostic_report_diagnostic): ... do it here instead.
All tests that use -fmax-errors now cause the compiler to cr
On Fri, 2016-10-14 at 15:50 -0400, Nathan Sidwell wrote:
> On 10/14/16 15:17, David Malcolm wrote:
>
> > "Limits the maximum number of error messages to @var{n}, at which
> > point
> > GCC bails out rather than attempting to continue processing the
> > source
> > code. If @var{n} is 0 (the defaul
On 10/14/16 15:17, David Malcolm wrote:
"Limits the maximum number of error messages to @var{n}, at which point
GCC bails out rather than attempting to continue processing the source
code. If @var{n} is 0 (the default), there is no limit on the number
of error messages produced. If @option{-Wf
On Thu, 2016-10-13 at 06:48 -0400, Nathan Sidwell wrote:
> On 10/11/16 16:07, David Malcolm wrote:
>
> > This logic is running when the next diagnostic is about to be
> > emitted.
> > But what if the user has selected -Wfatal-errors and there's a
> > single
> > error and no further diagnostics? C
On 10/11/16 16:07, David Malcolm wrote:
This logic is running when the next diagnostic is about to be emitted.
But what if the user has selected -Wfatal-errors and there's a single
error and no further diagnostics? Could this change the observable
behavior? (I'm trying to think of a case here,
On 10/11/16 16:07, David Malcolm wrote:
This logic is running when the next diagnostic is about to be emitted.
But what if the user has selected -Wfatal-errors and there's a single
error and no further diagnostics? Could this change the observable
behavior? (I'm trying to think of a case here,
On Tue, 2016-10-11 at 06:34 -0400, Nathan Sidwell wrote:
> Hi,
> Jonathan & I were chatting at the cauldron about how -fmax-errors
> kills any
> notes about the final error. That's because we bail out just after
> emitting the
> final error. This patch fixes the problem by bailing out just befo
