]> git.ipfire.org Git - thirdparty/gcc.git/commit
The flag diagnostic_context::some_warnings_are_errors controls whether
authormanu <manu@138bc75d-0d04-0410-961f-82ee72b054a4>
Mon, 14 Sep 2015 19:27:50 +0000 (19:27 +0000)
committermanu <manu@138bc75d-0d04-0410-961f-82ee72b054a4>
Mon, 14 Sep 2015 19:27:50 +0000 (19:27 +0000)
commit5e6392e809db05d347659bd40627f5fac4ade209
treed1111a6ca96f46cd25e7fb0b9fc44f1375d175e1
parentc999c2a78bd5898cbc73b3a3402d5fbb6004e6a1
The flag diagnostic_context::some_warnings_are_errors controls whether
to give the message "all warnings being treated as errors". However, when
warnings are buffered and then discarded, this flag is not reset. It turns
out we do not need this flag at all, since we already count explicitly how
many warnings were converted into errors, and this number is kept up to
date for the buffered diagnostics used by Fortran.

gcc/ChangeLog:

2015-09-14  Manuel López-Ibáñez  <manu@gcc.gnu.org>

PR fortran/67460
* diagnostic.c (diagnostic_initialize): Do not set
some_warnings_are_errors.
(diagnostic_finish): Use DK_WERROR count instead.
(diagnostic_report_diagnostic): Do not set
some_warnings_are_errors.
* diagnostic.h (struct diagnostic_context): Remove
some_warnings_are_errors.

gcc/testsuite/ChangeLog:

2015-09-14  Manuel López-Ibáñez  <manu@gcc.gnu.org>

PR fortran/67460
* gfortran.dg/pr67460.f90: New test.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@227760 138bc75d-0d04-0410-961f-82ee72b054a4
gcc/ChangeLog
gcc/diagnostic.c
gcc/diagnostic.h
gcc/testsuite/ChangeLog
gcc/testsuite/gfortran.dg/pr67460.f90 [new file with mode: 0644]