From: Joseph Myers <joseph@codesourcery.com>
To: Lewis Hyatt <lhyatt@gmail.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: Ping^2: 2 libcpp patches
Date: Tue, 16 Aug 2022 16:57:26 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2208161656440.369967@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAA_5UQ4Hqsy6Z2gBPM9oOuaUBkSncLmCuV4GDNPmGpquVYa+zQ@mail.gmail.com>
On Tue, 16 Aug 2022, Lewis Hyatt via Gcc-patches wrote:
> For the first patch, I think it is a worthwhile goal to fix all the
> places where libcpp fails to support UTF-8 correctly, and this is one
> of two remaining ones that I'm aware of. I can fix the other case
> (handling of #pragma push_macro) once this one is in place.
>
> The second patch is about libcpp not allowing raw strings containing
> newlines in preprocessor directives, which is a nearly decade-old
> glitch that I think is also worth addressing.
As these are both about C++ features, C++ maintainers might be best placed
to look at them.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-08-16 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 13:50 Lewis Hyatt
2022-08-16 16:57 ` Joseph Myers [this message]
2022-08-23 23:47 ` Lewis Hyatt
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=alpine.DEB.2.22.394.2208161656440.369967@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=lhyatt@gmail.com \
/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).