From: Ken Brown <kbrown@cornell.edu>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 23771@debbugs.gnu.org
Subject: bug#23771: Eliminating compiler warnings
Date: Wed, 22 Jun 2016 10:06:23 -0400 [thread overview]
Message-ID: <c04bc47a-8a56-7fc2-a992-b1e471f7033c@cornell.edu> (raw)
In-Reply-To: <5769E61B.9020200@cs.ucla.edu>
On 6/21/2016 9:12 PM, Paul Eggert wrote:
> Thanks for all the work in improving static checking for Cygwin builds.
> I just now checked the attached patch into master, which I hope improves
> on it. I tested it on Fedora (both with and without window systems).
Thanks. That's a big improvement.
> I had one problem with the recent changes, in that they suppressed all
> warnings about jumps over AUTO_STRING calls. That's pretty drastic, as
> the warnings are typically useful, so the attached patch reverts that.
> Can you let me know which call needs the warning suppressed in the
> Cygwin-specific code in the new master? I can suggest something which
> disables the warning just for that call.
It's in line 7057 of w32fns.c. I see that you fixed a similar warning
in xfns.c in commit e0400b7 by moving the AUTO_STRING call. I've just
done the same thing in commit bbc58fe.
Ken
next prev parent reply other threads:[~2016-06-22 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 2:04 bug#23771: Eliminating compiler warnings Ken Brown
2016-06-15 14:44 ` Eli Zaretskii
2016-06-16 1:38 ` Ken Brown
2016-06-16 15:14 ` Eli Zaretskii
2016-06-16 15:50 ` Paul Eggert
2016-06-21 3:11 ` Ken Brown
2016-06-22 1:12 ` Paul Eggert
2016-06-22 6:10 ` martin rudalics
2016-06-23 7:15 ` Paul Eggert
2016-06-22 14:04 ` Andy Moreton
2016-06-22 14:10 ` Ken Brown
2016-06-22 14:06 ` Ken Brown [this message]
2016-06-15 20:24 ` Richard Stallman
2016-06-16 1:41 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c04bc47a-8a56-7fc2-a992-b1e471f7033c@cornell.edu \
--to=kbrown@cornell.edu \
--cc=23771@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).