[Bug middle-end/71701] bogus token in -Wmaybe-uninitialized warning

[msebor at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71701

Martin Sebor  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  ---
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.

[Bug middle-end/71701] bogus token in -Wmaybe-uninitialized warning

[palves at redhat dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71701

--- Comment #5 from Pedro Alves  ---
See original context here, where the warning was truly puzzling:

 https://sourceware.org/ml/gdb-patches/2016-06/msg00515.html

[Bug middle-end/71701] bogus token in -Wmaybe-uninitialized warning

[palves at redhat dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71701

--- Comment #4 from Pedro Alves  ---
This was with: gcc version 7.0.0 20160503 (experimental) (GCC)

[Bug middle-end/71701] bogus token in -Wmaybe-uninitialized warning

[palves at redhat dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71701

--- Comment #3 from Pedro Alves  ---
Created attachment 38791
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38791&action=edit
Preprocessed testcase.