GNU bug report logs - #23771
Eliminating compiler warnings

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ken Brown <kbrown <at> cornell.edu>
Subject: bug#23771: closed (Re: bug#23771: Eliminating compiler warnings)
Date: Tue, 21 Jun 2016 03:12:01 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#23771: Eliminating compiler warnings

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 23771 <at> debbugs.gnu.org.

-- 
23771: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23771
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ken Brown <kbrown <at> cornell.edu>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: eggert <at> cs.ucla.edu, 23771-done <at> debbugs.gnu.org
Subject: Re: bug#23771: Eliminating compiler warnings
Date: Mon, 20 Jun 2016 23:11:03 -0400

Thanks for all the suggestions and corrections.  I've fixed everything 
(I hope) and pushed to master.

Closing.

[Message part 3 (message/rfc822, inline)]

From: Ken Brown <kbrown <at> cornell.edu>
To: bug-gnu-emacs <at> gnu.org
Subject: Eliminating compiler warnings
Date: Tue, 14 Jun 2016 22:04:28 -0400

[Message part 4 (text/plain, inline)]

I would like to get rid of all compiler warnings in the Cygwin builds 
(X11, w32, and nox).  There are currently none in the X11 build, but 
there are a lot in the other builds.  Many of the warnings in the w32 
build probably occur in the MinGW build also.  And all of the warnings 
in the nox build would occur in any build without a window system.

The seven patches attached attempt to eliminate all the currently 
existing warnings.  There is one patch for each type of warning.  Since 
they affect other platforms besides Cygwin, I won't install them until 
someone has had a chance to review them.  There's obviously no rush 
about this.

Two comments: First, patch 0006-... is there because there might be a 
jump over an AUTO_STRING call.  (This happens exactly once in the 
Cygwin-w32 build.)  It seems stupid to have to worry about this.  An 
alternative would be to just disable the -Wjump-misses-init warning.

Second, patch 0007-... is there because I couldn't think of a reasonable 
way to avoid -Waddress warnings when compiling w32fns.c, w32menu.c, and 
menu.c in the Cygwin-w32 build.  Everything I thought of would have made 
the code very ugly.  So I simply disabled that warning for the 
Cygwin-w32 build, and I took the liberty of doing the same thing for the 
MinGW build, which I think is also affected in some cases.  If someone 
sees a better way of eliminating those warnings, that would be preferable.

Ken

[0001-Eliminate-noreturn-warnings-if-there-s-no-window-sys.patch (text/plain, attachment)]

[0002-Fix-unused-variable-compiler-warnings.patch (text/plain, attachment)]

[0003-Avoid-empty-body-compiler-warnings.patch (text/plain, attachment)]

[0004-Fix-format-compiler-warnings.patch (text/plain, attachment)]

[0005-Don-t-define-unneeded-function-on-Cygwin.patch (text/plain, attachment)]

[0006-Avoid-jump-misses-init-compiler-warnings.patch (text/plain, attachment)]

[0007-Avoid-address-compiler-warnings.patch (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.