[prev in list] [next in list] [prev in thread] [next in thread]
List: gcc-bugs
Subject: [Bug middle-end/71701] bogus token in -Wmaybe-uninitialized warning
From: "msebor at gcc dot gnu.org via Gcc-bugs" <gcc-bugs () gcc ! gnu ! org>
Date: 2021-03-31 21:23:01
Message-ID: bug-71701-4-FiZE782J4u () http ! gcc ! gnu ! org/bugzilla/
[Download RAW message or body]
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.=
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic