From: Joseph Myers <josmyers@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [pushed] diagnostics, analyzer: add optional per-diagnostic property bags to SARIF
Date: Fri, 9 Feb 2024 16:53:02 +0000 (UTC) [thread overview]
Message-ID: <ed4abff-9c-1592-9fb-8d73156e2a6d@redhat.com> (raw)
In-Reply-To: <20231201135851.1841421-2-dmalcolm@redhat.com>
On Fri, 1 Dec 2023, David Malcolm wrote:
> * diagnostic-core.h (emit_diagnostic_valist): New overload decl.
This has broken regeneration of gcc.pot (overloads can't have the message
extracted for translation in different argument positions).
emit_diagnostic_valist used incompatibly as both --keyword=emit_diagnostic_valist:4
--flag=emit_diagnostic_valist:4:gcc-internal-format and --keyword=emit_diagnostic_valist:5
--flag=emit_diagnostic_valist:5:gcc-internal-format
See commit 6c8e584430bc5dc01b4438f3c38a2a10fcba7685 for previous fixes for
this involving the same function, or
40fecdd62f7d293a214dd71b81de5e0f1099bba7 and
db30e21cbff7b9b2acd13ab83e25e3bf52f9696f for older fixes for similar
issues.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-02-09 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 13:58 [pushed] docs: remove stray reference to -fanalyzer-checker=taint [PR103533] David Malcolm
2023-12-01 13:58 ` [pushed] diagnostics, analyzer: add optional per-diagnostic property bags to SARIF David Malcolm
2024-02-09 16:53 ` Joseph Myers [this message]
2024-02-13 2:11 ` [pushed] diagnostics: unbreak 'make gcc.pot' David Malcolm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed4abff-9c-1592-9fb-8d73156e2a6d@redhat.com \
--to=josmyers@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).