From: Jakub Jelinek <jakub@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Thomas Schwinge" <thomas@codesourcery.com>,
"Raiki Tamura" <tamaron1203@gmail.com>,
"Philip Herron" <herron.philip@googlemail.com>,
gcc@gcc.gnu.org, gcc-rust@gcc.gnu.org,
"David Edelsohn" <dje.gcc@gmail.com>,
"Arthur Cohen" <arthur.cohen@embecosm.com>,
"Arsen Arsenović" <arsen@aarsen.me>
Subject: Re: [GSoC] gccrs Unicode support
Date: Thu, 16 Mar 2023 14:07:35 +0100 [thread overview]
Message-ID: <ZBMUl6W830h+lfR9@tucnak> (raw)
In-Reply-To: <a476e56f825e8570a3f885491f871469879305c6.camel@klomp.org>
On Thu, Mar 16, 2023 at 01:58:57PM +0100, Mark Wielaard wrote:
> On Thu, 2023-03-16 at 10:28 +0100, Thomas Schwinge wrote:
> > I'm now also putting Mark Wielaard in CC; he once also started discussing
> > this topic, "thinking of importing a couple of gnulib modules to help
> > with UTF-8 processing [unless] other gcc frontends handle [these things]
> > already in a way that might be reusable". See the thread starting at
> > <https://inbox.sourceware.org/gcc/YPQrMBHyu3wRpT5o@wildebeest.org>
> > "rust frontend and UTF-8/unicode processing/properties".
>
> Thanks. BTW. I am not currently working on this.
> Note the responses in the above thread by Ian and Jason who pointed out
> that some of the requirements of the gccrs frontend might be covered in
> the go frontend and libcpp, but not really in a reusable way.
libcpp can be certainly linked into the gccrs FE and specific functions
called from it even if libcpp isn't used as a preprocessor for the language.
Small changes to libcpp are obviously possible as well to make it work.
Jakub
next prev parent reply other threads:[~2023-03-16 13:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 13:22 rust frontend and UTF-8/unicode processing/properties Mark Wielaard
2021-07-18 20:12 ` Ian Lance Taylor
2021-07-18 22:23 ` Jason Merrill
2021-07-23 11:29 ` Philip Herron
2021-07-29 19:46 ` Manuel López-Ibáñez
2023-03-13 16:18 ` [GSoC] gccrs Unicode support Raiki Tamura
2023-03-15 11:00 ` Philip Herron
2023-03-15 14:53 ` Arsen Arsenović
2023-03-15 15:18 ` Jakub Jelinek
2023-03-16 8:57 ` Raiki Tamura
2023-03-16 9:28 ` Thomas Schwinge
2023-03-16 12:58 ` Mark Wielaard
2023-03-16 13:07 ` Jakub Jelinek [this message]
2023-03-18 8:31 ` Raiki Tamura
2023-03-18 8:47 ` Jonathan Wakely
2023-03-18 8:59 ` Raiki Tamura
2023-03-18 9:28 ` Jakub Jelinek
2023-03-20 10:19 ` Raiki Tamura
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=ZBMUl6W830h+lfR9@tucnak \
--to=jakub@redhat.com \
--cc=arsen@aarsen.me \
--cc=arthur.cohen@embecosm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=herron.philip@googlemail.com \
--cc=mark@klomp.org \
--cc=tamaron1203@gmail.com \
--cc=thomas@codesourcery.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).