public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/49314] md5test, shatest output FAILs on Tru64 UNIX Date: Tue, 21 Jun 2011 12:11:00 -0000 [thread overview] Message-ID: <bug-49314-8172-a8kuul98ee@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49314-8172@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49314 --- Comment #14 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-06-21 12:09:30 UTC --- > The question now is what's a clean fix for this issue, rather than > hardcoding the result? I've now checked this with native and GNU iconv: feff.utf-8 is the input sequence from iconv_init: > od -x feff.utf-8 0000000 bbef 0abf At first everything seemed to work with both tools, except that I need byte swapping with native iconv, but not with GNU iconv: > /usr/bin/iconv -f UTF-8 -t UCS-2 < feff.utf-8 | od -x 0000000 feff 000a > /vol/gnu/bin/iconv -f UTF-8 -t UCS-2 < feff.utf-8 | od -x 0000000 fffe 0a00 But when I removed the newline from the input file, results differ: > od -x feff.utf-8-nonl 0000000 bbef 00bf > /usr/bin/iconv -f UTF-8 -t UCS-2 < feff.utf-8-nonl | od -x 0000000 feff feff > /vol/gnu/bin/iconv -f UTF-8 -t UCS-2 < feff.utf-8-nonl | od -x 0000000 fffe As result, I've simply added a padding NUL byte to the input sequence. This let the iconv succeed and my arraycopy testcase and both md5test and shatest pass. I'm running a full rebuild and check of libjava for good measure. Rainer
next prev parent reply other threads:[~2011-06-21 12:11 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-07 17:28 [Bug libgcj/49314] New: " ro at gcc dot gnu.org 2011-06-16 17:01 ` [Bug libgcj/49314] " ro at gcc dot gnu.org 2011-06-16 17:45 ` tromey at gcc dot gnu.org 2011-06-16 18:20 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-16 18:58 ` tromey at gcc dot gnu.org 2011-06-16 20:52 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-17 9:58 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-17 13:04 ` dominiq at lps dot ens.fr 2011-06-17 13:09 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-17 14:04 ` howarth at nitro dot med.uc.edu 2011-06-17 14:08 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-17 16:17 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-18 5:56 ` howarth at nitro dot med.uc.edu 2011-06-20 14:31 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-21 12:11 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2011-06-21 13:59 ` ro at gcc dot gnu.org 2011-06-21 17:11 ` ro at gcc dot gnu.org 2011-06-21 17:13 ` ro 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-49314-8172-a8kuul98ee@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).