Date: Sun, 5 Jan 2020 13:11:30 -0600 From: Warner Losh <imp@bsdimp.com> To: Ed Maste <emaste@freebsd.org> Cc: Pedro Giffuni <pfg@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r356367 - in head: . share/mk Message-ID: <CANCZdfowkugvJ21Nc8=SgohDShxsYLtqOxjuANFn=WpaiNJrYA@mail.gmail.com> In-Reply-To: <CAPyFy2AffKq8G1%2BX8WPKGcasetfjoWvF-LiX6TqoOj7WZD6DNA@mail.gmail.com> References: <202001050247.0052lu11098031@repo.freebsd.org> <0b3ae104-ea62-1aa8-c926-c6021565a050@FreeBSD.org> <CAPyFy2AffKq8G1%2BX8WPKGcasetfjoWvF-LiX6TqoOj7WZD6DNA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 5, 2020, 11:21 AM Ed Maste <emaste@freebsd.org> wrote: > On Sun, 5 Jan 2020 at 13:16, Pedro Giffuni <pfg@freebsd.org> wrote: > > > > It's really nice how the compiler warning trend went down. > > > > On FreeBSD-head-mips-build* it went from 7691 warnings to 473 + 83. > > Thanks for mentioning that. Continuing to support ancient GCC is a > drag on everyone using a contemporary compiler for development > (in-tree or external toolchain) and thus I stuck with Warner's > original timeline even though there are a few warts to resolve on some > archs still. > And the warts are generally adequately resolved by external toolchain. Except for sparc64, for which nobody has done any nontrivial work on for this transition. All the other architects have had most of this issues identified with process resolved, or well on the way to resolution. This total lack of work on sparc64 may result in an accelerated timeline for its removal. Warner >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfowkugvJ21Nc8=SgohDShxsYLtqOxjuANFn=WpaiNJrYA>