From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Warnings in mingw64 builds on master
Date: Sun, 16 Aug 2020 20:08:05 +0300 [thread overview]
Message-ID: <83zh6uh62y.fsf@gnu.org> (raw)
In-Reply-To: <87tux2sfo4.fsf@telefonica.net> (message from Óscar Fuentes on Sun, 16 Aug 2020 18:45:31 +0200)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Sun, 16 Aug 2020 18:45:31 +0200
>
> The information gained about the contents of fd_info[fd] from that test
> is discarded when the compiler finds a call to an external function
> (DebPrint) a few lines below, since DebPrint (or one of the functions it
> calls) might change the contents of the global fd_info array.
>
> If the OP was not building with EMACSDEBUG defined, the warning would be
> bogus indeed, since DebPrint is a no-op on that case.
I expect Andy was building without EMACSDEBUG, since he was almost
certainly building an optimized binary, see below.
> which compiled with `gcc -c -Wall -Wmaybe-uninitialized' (gcc 10.1)
> shows no warnings
I think you need to use -O2 (or some optimization switch) to have this
warning. At least that's how it used to be in the past, I don't have
GCC 10 installed to check.
next prev parent reply other threads:[~2020-08-16 17:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 22:37 Warnings in mingw64 builds on master Andy Moreton
2020-08-15 16:24 ` Eli Zaretskii
2020-08-15 18:48 ` Andy Moreton
2020-08-15 19:03 ` Eli Zaretskii
2020-08-15 19:39 ` Andy Moreton
2020-08-15 20:36 ` Óscar Fuentes
2020-08-16 2:31 ` Eli Zaretskii
2020-08-16 11:21 ` Andy Moreton
2020-08-16 14:44 ` Eli Zaretskii
2020-08-16 16:45 ` Óscar Fuentes
2020-08-16 17:08 ` Eli Zaretskii [this message]
2020-08-16 15:05 ` Óscar Fuentes
2020-08-15 22:34 ` Paul Eggert
2020-08-16 2:31 ` Eli Zaretskii
2020-08-16 15:25 ` Paul Eggert
2020-08-16 15:39 ` Eli Zaretskii
2020-08-17 4:21 ` Paul Eggert
2020-08-17 16:21 ` Eli Zaretskii
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=83zh6uh62y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).