public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sbergman at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/104030] New: -Wbidi-chars should not warn about UCNs
Date: Fri, 14 Jan 2022 14:51:47 +0000 [thread overview]
Message-ID: <bug-104030-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104030
Bug ID: 104030
Summary: -Wbidi-chars should not warn about UCNs
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: preprocessor
Assignee: unassigned at gcc dot gnu.org
Reporter: sbergman at redhat dot com
Target Milestone: ---
As discussed in the sub-thread starting at
<https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585710.html> "Re:
[PATCH] libcpp: Implement -Wbidi-chars for CVE-2021-42574 [PR103026]",
-Wbidi-chars should not emit warnings when the problematic characters are
written as UCNs rather than verbatim. For example, the line
> aText = u"\u202D" + aText;
found in the LibreOffice source code should not cause a warning (which couldn't
even be silenced with a local `#pragma GCC diagnostic ignored "-Wbidi-chars"`
due to bug 53431).
next reply other threads:[~2022-01-14 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:51 sbergman at redhat dot com [this message]
2022-01-14 14:55 ` [Bug preprocessor/104030] [12 Regression] " mpolacek at gcc dot gnu.org
2022-01-14 14:59 ` jakub at gcc dot gnu.org
2022-01-14 15:00 ` jakub at gcc dot gnu.org
2022-01-14 15:05 ` mpolacek at gcc dot gnu.org
2022-01-14 15:07 ` mpolacek at gcc dot gnu.org
2022-01-14 15:30 ` jakub at gcc dot gnu.org
2022-01-14 15:41 ` sbergman at redhat dot com
2022-01-18 13:52 ` rguenth at gcc dot gnu.org
2022-01-24 22:49 ` cvs-commit at gcc dot gnu.org
2022-01-24 22:50 ` mpolacek 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-104030-4@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).