public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/104030] [12 Regression] -Wbidi-chars should not warn about UCNs
Date: Fri, 14 Jan 2022 15:05:53 +0000	[thread overview]
Message-ID: <bug-104030-4-geoBLaoqnZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104030-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Either we drop the UCN support altogether, or make -Wbidi-chars a 2 level
> warning, -Wbidi-chars mapping to -Wbidi-chars=1 which doesn't warn about
> UCNs and
> -Wbidi-chars=2 that does.

Exactly.  Except I'm not sure how well that will play with the rest of the
-Wbidi-chars= suboptions.  :/

Like,

-Wbidi-chars=any -Wbidi-chars=2

should probably warn about any bidi chars, including UCNs, but the latter
option might cause it to be just -Wbidi-chars=unpaired, but warn about UCNs.

  parent reply	other threads:[~2022-01-14 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 14:51 [Bug preprocessor/104030] New: " sbergman at redhat dot com
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 [this message]
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-geoBLaoqnZ@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).