From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 23BFE3858D35; Sat, 25 Mar 2023 01:57:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 23BFE3858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679709445; bh=Vc+rsFNF8VkruPCKJnYBk/XAPRVQgg24Q9gJVH2kxHs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YVZPFC9EtMbCRP7Swrogi40qxyyuLffYHrLSCoJ6Ic4moN2Y0UYiH3G5Opg4Xq9Eg A/KYU9+NIiyAdS03C8PlkuQo9SDR0DgRQ32gZat+1S9EyhglBojKcj2NbFDABWT79s htmSHcR/7S1yzFP3dZm8Ez/9ITIRXlm12dIJrthk= From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/109098] Encoding errors on SARIF output for non-UTF-8 source files Date: Sat, 25 Mar 2023 01:57:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109098 --- Comment #8 from Hans-Peter Nilsson --- (In reply to David Malcolm from comment #7) > The invalid UTF-8 in the patch seems to have broken the server-side scrip= t: Maybe the not-really-utf8 files need to be marked in some way in the git re= po to be safely handled for future checkout and updates, including the problem= atic scripting? However, reading gitattributes(5) it's not obvious how.=