This is the mail archive of the gcc@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: Warning annoyances in list_read.c


On Mon, Mar 27, 2017 at 07:41:12PM +0200, Marek Polacek wrote:
> On Mon, Mar 27, 2017 at 07:33:05PM +0200, Toon Moene wrote:
> > On 03/27/2017 06:45 PM, Marek Polacek wrote:
> > 
> > > On Mon, Mar 27, 2017 at 09:27:34AM -0700, Steve Kargl wrote:
> > 
> > > > But that's okay.  I now understand that it is acceptable for
> > > > a developer to commit a change that causes issues for other
> > > > developers, and said developer can turn a blind eye.
> > > 
> > > Nonsense.
> > 
> > The person developing the warning could *at least* have bootstrapped all
> > languages and detected, warned and helped the Fortran/Ada/whatever side to
> > cope with it.
> 
> Of course "the person" had bootstrapped and tested all the languages before
> adding the warning.  If only any of you bothered to check the fortran/
> ChangeLogs:
> 

fortran/ != libgfortran/

"The person" also failed to post his changes to fortran/
on the fortran@ mailing list.  So, the fortran changes were
likely not reviewed.

-- 
Steve
20161221 https://www.youtube.com/watch?v=IbCHE-hONow


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