public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/71701] bogus token in -Wmaybe-uninitialized warning
[not found] <bug-71701-4@http.gcc.gnu.org/bugzilla/>
@ 2021-03-31 21:23 ` msebor at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: msebor at gcc dot gnu.org @ 2021-03-31 21:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71701
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |9.3.0
Version|7.0 |9.0
Target Milestone|--- |9.0
Resolution|--- |FIXED
CC| |msebor at gcc dot gnu.org
Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning has disappeared with r263660 (9.0.0 20180820): PR c++/78655 (gcc
doesn't exploit the fact that the result of pointer addition can not be
nullptr)
I could only reproduce it with the preprocessed test case from attachment
38791. Since it depends on the contents of Glibc headers I'm going to resolve
it as fixed without adding a test case.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-03-31 21:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-71701-4@http.gcc.gnu.org/bugzilla/>
2021-03-31 21:23 ` [Bug middle-end/71701] bogus token in -Wmaybe-uninitialized warning msebor at gcc dot gnu.org
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).