From: Thomas Schwinge <thomas@codesourcery.com>
To: Raiki Tamura <tamaron1203@gmail.com>,
Jakub Jelinek <jakub@redhat.com>,
Philip Herron <herron.philip@googlemail.com>
Cc: 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>,
"Mark Wielaard" <mark@klomp.org>
Subject: Re: [GSoC] gccrs Unicode support
Date: Thu, 16 Mar 2023 10:28:39 +0100 [thread overview]
Message-ID: <87lejxujso.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <ZBHhutUTOl26A13z@tucnak>
Hi!
(By the way, this GSoC project is being discussed in GCC/Rust Zulip:
<https://gcc-rust.zulipchat.com/#narrow/stream/327528-GSoC/topic/Unicode.20support>.)
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".
On 2023-03-15T16:18:18+0100, Jakub Jelinek via Gcc <gcc@gcc.gnu.org> wrote:
> On Wed, Mar 15, 2023 at 11:00:19AM +0000, Philip Herron via Gcc wrote:
>> Excellent work on getting up to speed on the rust front-end. From my
>> perspective I am interested to see what the wider GCC community thinks
>> about using https://www.gnu.org/software/libunistring/ library within GCC
>> instead of rolling our own, this means it will be another dependency on GCC.
>>
>> The other option is there is already code in the other front-ends to do
>> this so in the worst case it should be possible to extract something out of
>> them and possibly make this a shared piece of functionality which we can
>> mentor you through.
>
> I don't know what exactly Rust FE needs in this area, but e.g. libcpp
> already handles whatever C/C++ need from Unicode support POV and can handle
> it without any extra libraries.
> So, if we could avoid the extra dependency, it would be certainly better,
> unless you really need massive amounts of code from those libraries.
> libcpp already e.g. provides mapping of unicode character names to code
> points, determining which unicode characters can appear at the start or
> in the middle of identifiers, etc.
So that's exactly the answer that I supposed you or someone else would
give. ;-)
That means, GCC/Rust has some investigation to do: whether what libcpp
contains is (a) sufficient for its needs, and (b) whether that code can
be reused/extracted/refactored in a sensible way, into GCC-level shared
source code file, to be used by several front ends (possibly via libcpp).
(I suppose GCC/Rust shouldn't link in libcpp directly.)
Thanks for the input, all!
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2023-03-16 9:28 UTC|newest]
Thread overview: 17+ 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
[not found] ` <d5e7434b-80e8-2817-ed87-a23ef2ac0cbb@uma.es>
[not found] ` <CAOWUKr0Sd3RRSy2cuqMLj--KTWqOz=nQMxmx7ahM8YunrFzEig@mail.gmail.com>
2023-03-15 11:00 ` [GSoC] gccrs Unicode support 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 [this message]
2023-03-16 12:58 ` Mark Wielaard
2023-03-16 13:07 ` Jakub Jelinek
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
2023-03-31 10:27 [GSoC] gccrs Unicode Support E M
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=87lejxujso.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.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=jakub@redhat.com \
--cc=mark@klomp.org \
--cc=tamaron1203@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).