UTF-16 streams

Tom Cook tom.k.cook@gmail.com
Thu Feb 5 10:30:00 GMT 2015

Confirmed that this also fails with gcc trunk (as of about 5AM UTC
today).  The stack trace is the same.  Is there something I need to do
to use the ctype<char16_t> you've added?

Actually I can't spot that template specialisation in the trunk code
(ie `grep -r 'ctype.*char16_t.*'` returns no matches, either in the
source or in $HOME/gcc-5.0/include).  If you could have a look and see
if it's sitting in a workspace somewhere, I'd be grateful.


On Thu, Feb 5, 2015 at 5:37 PM, Tom Cook <tom.k.cook@gmail.com> wrote:
> Thanks, Jonathan.  I'm currently building the GCC trunk to see where it gets me.
> I'm not at all certain, by the way, that the standard requires this -
> I don't have ready access to a copy.
> As a side note, it would be useful if
> https://gcc.gnu.org/wiki/InstallingGCC mentioned whether the build
> works using eg 'make -j 5'.
> Regards,
> Tom
> On Thu, Feb 5, 2015 at 3:15 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>> On 4 February 2015 at 23:38, Tom Cook wrote:
>>> A more specific question: is providing a specialisation of std::ctype
>>> (ie std::ctype<char16_t>) the right way to fix this?
>> I've just used an online compiler that provides GCC trunk and still
>> get a bad_cast exception. It doesn't compile using Clang and libc++,
>> so it might be that your program is not required to work and you do
>> need to provide some user-defined specializations.
>> I won't be able to check the standard or debug it until next week.

More information about the Libstdc++ mailing list