public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gnugcc at marino dot st" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/67096] libstdc++ testsuite, codecvt: many UTF-8 tests illegal (testing bytes 5 and 6)
Date: Sun, 13 Sep 2015 16:23:00 -0000	[thread overview]
Message-ID: <bug-67096-4-ARspWBnJ7w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67096-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67096

--- Comment #5 from John Marino <gnugcc at marino dot st> ---
Hmmm, thinking about this, I'd bet Linux would FAIL this test.  It probably
does allow 6-bytes (even though it should not) and thus K would return 6.

I don't really have a recommendation -- the standard is pretty clear, 4 bytes
is the maximum for UTF-8, so it probably should fail on Linux.

Or maybe this whole test should just be removed?  What's it really testing that
the other tests haven't already?


      parent reply	other threads:[~2015-09-13 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-02 13:57 [Bug libstdc++/67096] New: " gnugcc at marino dot st
2015-08-02 14:07 ` [Bug libstdc++/67096] " gnugcc at marino dot st
2015-08-03 15:23 ` redi at gcc dot gnu.org
2015-09-11 12:11 ` redi at gcc dot gnu.org
2015-09-11 13:07 ` redi at gcc dot gnu.org
2015-09-11 13:12 ` redi at gcc dot gnu.org
2015-09-13 13:49 ` gnugcc at marino dot st
2015-09-13 16:23 ` gnugcc at marino dot st [this message]

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-67096-4-ARspWBnJ7w@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: 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).