public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug other/92435] % format codes for diagnostics are not documented in the GCC internals manual
[not found] <bug-92435-4@http.gcc.gnu.org/bugzilla/>
@ 2021-09-12 8:37 ` egallager at gcc dot gnu.org
2021-09-15 20:50 ` msebor at gcc dot gnu.org
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: egallager at gcc dot gnu.org @ 2021-09-12 8:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92435
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org,
| |dodji at gcc dot gnu.org,
| |egallager at gcc dot gnu.org,
| |roland.illig at gmx dot de
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
cc-ing relevant people
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug other/92435] % format codes for diagnostics are not documented in the GCC internals manual
[not found] <bug-92435-4@http.gcc.gnu.org/bugzilla/>
2021-09-12 8:37 ` [Bug other/92435] % format codes for diagnostics are not documented in the GCC internals manual egallager at gcc dot gnu.org
@ 2021-09-15 20:50 ` msebor at gcc dot gnu.org
2021-09-16 17:43 ` egallager at gcc dot gnu.org
2021-10-24 17:08 ` egallager at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: msebor at gcc dot gnu.org @ 2021-09-15 20:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92435
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-09-15
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
See also the following question:
https://gcc.gnu.org/pipermail/gcc/2021-September/237281.html
It would be helpful to document the GCC specific directives somewhere. The
-Wformat-diag GCC-developer warning option could also stand to be documented.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug other/92435] % format codes for diagnostics are not documented in the GCC internals manual
[not found] <bug-92435-4@http.gcc.gnu.org/bugzilla/>
2021-09-12 8:37 ` [Bug other/92435] % format codes for diagnostics are not documented in the GCC internals manual egallager at gcc dot gnu.org
2021-09-15 20:50 ` msebor at gcc dot gnu.org
@ 2021-09-16 17:43 ` egallager at gcc dot gnu.org
2021-10-24 17:08 ` egallager at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: egallager at gcc dot gnu.org @ 2021-09-16 17:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92435
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #3)
> See also the following question:
> https://gcc.gnu.org/pipermail/gcc/2021-September/237281.html
> It would be helpful to document the GCC specific directives somewhere. The
> -Wformat-diag GCC-developer warning option could also stand to be documented.
Yeah I was trying to convince the Wesnoth devs to look at -Wformat-diag for
inspiration for their own message-strings linter, but since it wasn't
documented, they didn't really know what to do, so I agree that documenting
that would be useful, too
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug other/92435] % format codes for diagnostics are not documented in the GCC internals manual
[not found] <bug-92435-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2021-09-16 17:43 ` egallager at gcc dot gnu.org
@ 2021-10-24 17:08 ` egallager at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: egallager at gcc dot gnu.org @ 2021-10-24 17:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92435
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org,
| |qing.zhao at oracle dot com
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
This mailing list message says to look in the commentary in cp/error.c or
c/c-objc-common.c:
https://gcc.gnu.org/pipermail/gcc-patches/2021-October/582162.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-10-24 17:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-92435-4@http.gcc.gnu.org/bugzilla/>
2021-09-12 8:37 ` [Bug other/92435] % format codes for diagnostics are not documented in the GCC internals manual egallager at gcc dot gnu.org
2021-09-15 20:50 ` msebor at gcc dot gnu.org
2021-09-16 17:43 ` egallager at gcc dot gnu.org
2021-10-24 17:08 ` egallager 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).