From: Raiki Tamura <tamaron1203@gmail.com>
To: gcc@gcc.gnu.org
Subject: [GSoC] gccrs Unicode support
Date: Tue, 14 Mar 2023 01:18:31 +0900 [thread overview]
Message-ID: <CAOWUKr0Sd3RRSy2cuqMLj--KTWqOz=nQMxmx7ahM8YunrFzEig@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hello,
My name is Raiki Tamura, an undergraduate student at Kyoto University in
Japan and I want to work on Unicode support in gccrs this year.
I have already written my proposal (linked below) and shared it with the
gccrs team in Zulip.
In the project, I am planning to use the GNU unistring library to handle
Unicode characters and the GNU IDN library to normalize identifiers.
According to my potential mentor, it would provide Unicode libraries for
all frontends in GCC. If there are concerns or feedback about this, please
tell me about it.
Thank you.
Link to my proposal:
https://docs.google.com/document/d/1MgsbJMF-p-ndgrX2iKeWDR5KPSWw9Z7onsHIiZ2pPKs/edit?usp=sharing
Raiki Tamura
next prev reply other threads:[~2023-03-13 16:18 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 ` Raiki Tamura [this message]
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
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
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='CAOWUKr0Sd3RRSy2cuqMLj--KTWqOz=nQMxmx7ahM8YunrFzEig@mail.gmail.com' \
--to=tamaron1203@gmail.com \
--cc=gcc@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).