public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/109098] Encoding errors on SARIF output for non-UTF-8 source files
Date: Mon, 13 Mar 2023 21:46:27 +0000	[thread overview]
Message-ID: <bug-109098-4-LloLNZagLK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109098-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
For diagnosis of non-UTF-8 in strings / comments, see commit 
0b8c57ed40f19086e30ce54faec3222ac21cc0df, "libcpp: Add -Winvalid-utf8 
warning [PR106655]" (implementing a new C++ requirement).

  parent reply	other threads:[~2023-03-13 21:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11  0:22 [Bug analyzer/109098] New: " dmalcolm at gcc dot gnu.org
2023-03-11  0:24 ` [Bug analyzer/109098] " dmalcolm at gcc dot gnu.org
2023-03-11  0:26 ` pinskia at gcc dot gnu.org
2023-03-11  0:28 ` pinskia at gcc dot gnu.org
2023-03-11  0:31 ` dmalcolm at gcc dot gnu.org
2023-03-11  0:33 ` dmalcolm at gcc dot gnu.org
2023-03-11  0:55 ` hp at gcc dot gnu.org
2023-03-13 21:46 ` joseph at codesourcery dot com [this message]
2023-03-25  1:01 ` dmalcolm at gcc dot gnu.org
2023-03-25  1:57 ` hp at gcc dot gnu.org
2023-03-27 15:34 ` dmalcolm at gcc dot gnu.org

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=bug-109098-4-LloLNZagLK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).