From: Kris Van Hees <kris.van.hees@oracle.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] utf-16 and utf-32 support in C and C++
Date: Thu, 13 Mar 2008 20:14:00 -0000 [thread overview]
Message-ID: <20080313195854.GF19427@oracle.com> (raw)
In-Reply-To: <de8d50360803131245k16a767abn84f92ddd41931466@mail.gmail.com>
On Thu, Mar 13, 2008 at 12:45:36PM -0700, Andrew Pinski wrote:
> On Thu, Mar 13, 2008 at 12:32 PM, Kris Van Hees
> <kris.van.hees@oracle.com> wrote:
> > This patch provides an implementation for support of UTF-16 and UTF-32
> > character data types in C and C++, based on the ISO/IEC draft technical
> > report for C (ISO/IEC JTC1 SC22 WG14 N1040) and the proposal for C++
> > (ISO/IEC JTC1 SC22 WG21 N2249). Neither proposal defines a specific
> > encoding for UTF-16. This implementation uses the target endianness
> > to determine whether UTF-16BE or UTF-16LE will be used.
>
> I have a couple of questions about the ABI with this patch, how does
> char16_t and char32_t get mangled for C++ code. Is this documented
> anywhere? How does promotion work with these types in C++ and C and
> is this tested? I remember reading the technical draft for C and it
> mentioned that the size does not have to exactly 16 (or 32) bytes, so
> it might be best if you added documentation to the extension page
> about this extension.
Let me get back to you on this, because I probably should solve the
following first...
> I don't see any of the testcases attached.
Oops - that is a stupid mistake on my end. Generated the diff without
having it include new files. I'll correct that immediately.
Kris
next prev parent reply other threads:[~2008-03-13 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 19:33 Kris Van Hees
2008-03-13 19:34 ` Kris Van Hees
2008-03-13 19:56 ` Andrew Pinski
2008-03-13 20:14 ` Kris Van Hees [this message]
2008-03-13 20:34 ` Kris Van Hees
2008-03-14 1:14 ` Joseph S. Myers
2008-03-13 19:59 ` Paul Koning
2008-03-13 19:59 ` Andrew Pinski
2008-03-14 1:18 ` Joseph S. Myers
2008-03-15 2:57 ` Tom Tromey
2008-03-22 15:33 ` Jason Merrill
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=20080313195854.GF19427@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@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).