From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: New warnings on emacs-26 branch with gcc 8.2.0 Date: Sun, 05 Aug 2018 23:23:32 +0100 Message-ID: <8636vsxxjv.fsf@gmail.com> References: <86a7q0ai2z.fsf@gmail.com> <6d36dc4c-1e14-b6c8-e2f0-911d08f759e1@cs.ucla.edu> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1533507708 15443 195.159.176.226 (5 Aug 2018 22:21:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 5 Aug 2018 22:21:48 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (windows-nt) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 06 00:21:44 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fmRPC-0003uL-OA for ged-emacs-devel@m.gmane.org; Mon, 06 Aug 2018 00:21:42 +0200 Original-Received: from localhost ([::1]:59952 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fmRRJ-0001Xz-EC for ged-emacs-devel@m.gmane.org; Sun, 05 Aug 2018 18:23:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40154) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fmRRC-0001Xt-Qm for emacs-devel@gnu.org; Sun, 05 Aug 2018 18:23:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fmRR9-0000Ns-Li for emacs-devel@gnu.org; Sun, 05 Aug 2018 18:23:46 -0400 Original-Received: from [195.159.176.226] (port=40417 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fmRR9-0000NW-Dz for emacs-devel@gnu.org; Sun, 05 Aug 2018 18:23:43 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fmRP0-0003jf-34 for emacs-devel@gnu.org; Mon, 06 Aug 2018 00:21:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 34 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:d1uSZ+iyQO8EfCibrIvvYyv11GY= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:228199 Archived-At: On Sun 05 Aug 2018, Paul Eggert wrote: > Andy Moreton wrote: > >> cc1.exe: warning: -Wabi won't warn about anything [-Wabi] >> cc1.exe: note: -Wabi warns about differences from the most up-to-date ABI, which is also used by default >> cc1.exe: note: use e.g. -Wabi=11 to warn about changes from GCC 7 > > I noticed this problem a while ago on Fedora in several GNU projects, and > fixed it for Emacs master in commit 2018-06-30T00:31:04!eggert@cs.ucla.edu. Thanks. I don't see these -Wabi warning on master. > To avoid the problem entirely in the emacs-26 I'd run admin/merge-gnulib and > update everything from Gnulib as it's not worth the trouble to cherry-pick > these sorts of fixes from master. If we'd rather not do admin/merge-gnulib, > then we can just suggest './configure --disable-gcc-warnings' and/or 'make > WERROR_CFLAGS=' to emacs-26 developers; either of these should work around the > problem. (Builders from tarballs needn't worry about this, as GCC warnings are > disabled for them by default.) That's a decision for the maintainers, but I think it would be useful to fix this if possible. >> Can this be simplified to be less over-zealous and less time consuming ? > The overzealous-warning part has been fixed on master. I'm sure 'configure' > could be sped up, if someone wants to take the time to work on that. Of the 562 "checking" lines when running configure on master, 146 of them are "checking whether C compiler handles -W*". This is excessively time consuming. Can gnulib not do less work to acheive this end, or do the work more efficiently ? AndyM