public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "delrieutheo at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/66855] New: codecvt wrong endianness in UTF-16 conversions Date: Mon, 13 Jul 2015 11:19:00 -0000 [thread overview] Message-ID: <bug-66855-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66855 Bug ID: 66855 Summary: codecvt wrong endianness in UTF-16 conversions Product: gcc Version: 5.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: delrieutheo at gmail dot com Target Milestone: --- Created attachment 35965 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35965&action=edit The buggy one There is a problem with codecvt, the facet codecvt_utf8_utf16 should do big-endian conversions with default template arguments. However this is the output I get linking with libstdc++-5.1.1 : UTF-16 [b098] [b294] [d0dc] [c624] UTF-16 to UTF-8 [eb] [82] [98] [eb] [8a] [94] [ed] [83] [9c] [ec] [98] [a4] Converting back to UTF-16 [98b0] [94b2] [dcd0] [24c6] The same code gives the expected result on OS X with libc++ and on Windows. When I specify the third template argument of codecvt_utf8_utf16 with std::little_endian, it gives the expected output.
next reply other threads:[~2015-07-13 11:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-13 11:19 delrieutheo at gmail dot com [this message] 2015-07-13 20:08 ` [Bug libstdc++/66855] " redi at gcc dot gnu.org 2015-07-13 20:10 ` redi at gcc dot gnu.org 2015-09-03 15:11 ` redi at gcc dot gnu.org 2015-09-03 15:12 ` redi at gcc dot gnu.org
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=bug-66855-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).