From: "Manuel López-Ibáñez" <manuel.lopez-ibanez@uma.es>
To: mark@klomp.org, "gcc@gnu.org" <gcc@gnu.org>
Subject: Re: rust frontend and UTF-8/unicode processing/properties
Date: Thu, 29 Jul 2021 21:46:14 +0200 [thread overview]
Message-ID: <d5e7434b-80e8-2817-ed87-a23ef2ac0cbb@uma.es> (raw)
> For the gcc rust frontend I was thinking of importing a couple of
> gnulib modules to help with UTF-8 processing, conversion to/from
> unicode codepoints and determining various properties of those
> codepoints. But it seems gcc doesn't yet have any gnulib modules
> imported, and maybe other frontends already have helpers to this that
> the gcc rust frontend could reuse.
Although I agree that factoring out the code in libcpp so that it can be used
by other FEs would be great and in line with the goals of
https://gcc.gnu.org/wiki/ModularGCC that is a significant amount of work.
Importing gnulib has its own advantages and it would allow GCC to finally
deprecate libiberty:
https://gcc.gnu.org/wiki/replacelibibertywithgnulib
There is a preliminary patch here:
https://gcc.gnu.org/legacy-ml/gcc-patches/2016-08/msg01554.html
Cheers,
Manuel.
next prev reply other threads:[~2021-07-29 19:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 13:22 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 [this message]
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
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=d5e7434b-80e8-2817-ed87-a23ef2ac0cbb@uma.es \
--to=manuel.lopez-ibanez@uma.es \
--cc=gcc@gnu.org \
--cc=mark@klomp.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).