This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/81306] valgrind error for function warn_for_multistatement_macros in file c-warn.c line 2474
- From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 26 Jul 2017 09:15:40 +0000
- Subject: [Bug c/81306] valgrind error for function warn_for_multistatement_macros in file c-warn.c line 2474
- Auto-submitted: auto-generated
- References: <bug-81306-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81306
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I've reproduced the issue but don't know what to do about it, it doesn't seem
to be a bug in the warning. I looks like the macro maps contains holes:
cc1: note: token 77 has x-location == y-location == 0
78: 0, 0
cc1: note: token 78 has x-location == y-location == 0
79: 0, 0
cc1: note: token 79 has x-location == y-location == 0
80: 0, 0
cc1: note: token 80 has x-location == y-location == 0
81: 0, 0
cc1: note: token 81 has x-location == y-location == 0
82: 0, 0
cc1: note: token 82 has x-location == y-location == 0
83: 0, 0
cc1: note: token 83 has x-location == y-location == 0
84: 0, 0
cc1: note: token 84 has x-location == y-location == 0
85: 0, 0
cc1: note: token 85 has x-location == y-location == 0
86: 0, 0
cc1: note: token 86 has x-location == y-location == 0
87: 0, 0
cc1: note: token 87 has x-location == y-location == 0
88: 0, 0
cc1: note: token 88 has x-location == y-location == 0
89: 0, 0
cc1: note: token 89 has x-location == y-location == 0
90: 0, 0
cc1: note: token 90 has x-location == y-location == 0