https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #14 from Martin Sebor ---
At -O1, GCC 8 as well as trunk print:
pr71157.i: In function ‘TeX_commands’:
pr71157.i:8469:44: warning: ‘TEX_clgrp’ may be used uninitialized in this
function [-Wmaybe-uninitialized]
8469 | while (*p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #13 from Martin Sebor ---
In GCC 9 the warning has disappeared with r263981.
At -O1, GCC 8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #12 from Martin Sebor ---
(In reply to Manuel López-Ibáñez from comment #10)
Yes, the warning should use the %G directive. It might be worth reviewing all
the middle-end warnings for this improvement. Unless we get rid of %G/%K
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #11 from Marc Glisse ---
Trunk doesn't show the warning (gcc-8 does).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
Manuel López-Ibáñez changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #9 from Paul Eggert ---
(In reply to Eric Gallager from comment #8)
> Try marking it up with __attribute__((returns_nonnull)) and/or
> __attribute__((nonnull)). If the first one works, then it's a case where GCC
> should suggest it,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #6 from Paul Eggert ---
> this is because it thinks skip_space() may return NULL:
That sounds like a bug, then, as skip_spaces immediately dereferences its
argument, so it cannot possibly return NULL.
Also, skip_spaces is never
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #4 from Paul Eggert ---
I worked around the GCC bug by applying the attached file etags.c.patch to GNU
Emacs. etags.c.patch replaces some weird but valid C code (add a small constant
to a pointer and test whether the resulting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #3 from Paul Eggert ---
Created attachment 38532
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38532=edit
patched version of e.i that avoids GCC bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #2 from Paul Eggert ---
Created attachment 38531
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38531=edit
GNU Emacs lib-src/etags.c patch to work around GCC bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
14 matches
Mail list logo
