From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 47080-done@debbugs.gnu.org
Subject: bug#47080: 28.0.50; Spurious variable left uninitialized compiler warning
Date: Fri, 12 Mar 2021 19:37:35 -0500 [thread overview]
Message-ID: <jwvr1kjc2pz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87im5vzz9e.fsf@web.de> (Michael Heerdegen's message of "Sat, 13 Mar 2021 01:13:49 +0100")
>> Indeed, the warning could even be generalized to other trivial constant
>> values like `t`, but I think what we have already gives enough false
>> positives ;-)
> FWIW, I also got one or two true positives in my own stuff.
> To avoid false positives, is it possible to limit the warning to "human
> written" code or to code that is not the result of macro expansion?
It's somewhere between difficult and impossible with the current setup.
Hygienic macro systems should be able to get that information, but
our macro system doesn't keep track of it.
It would require efforts similar to those needed to preserve
file+line+col information.
Stefan
next prev parent reply other threads:[~2021-03-13 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 0:04 bug#47080: 28.0.50; Spurious variable left uninitialized compiler warning Michael Heerdegen
2021-03-12 0:23 ` Lars Ingebrigtsen
2021-03-12 0:39 ` Michael Heerdegen
2021-03-12 2:58 ` Stefan Monnier
2021-03-12 3:07 ` Lars Ingebrigtsen
2021-03-12 3:29 ` Stefan Monnier
2021-03-13 0:13 ` Michael Heerdegen
2021-03-13 0:37 ` Stefan Monnier [this message]
2021-03-13 0:44 ` Michael Heerdegen
2021-03-13 0:58 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvr1kjc2pz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=47080-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.