public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/52539] I/O: Wrong result for UTF-8/UCS-4 list-directed and namelist read and nml write
Date: Sun, 27 Apr 2014 11:38:00 -0000	[thread overview]
Message-ID: <bug-52539-4-DGgQd71KnF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52539-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52539

--- Comment #13 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #12)
> ! { dg-do run }
[...]

Which is essentially the following.

-str = 4_'a'//char (int (z'4F60'),4)     &
+str = 4_'1a'//char (int (z'4F60'),4)     &

If that's sufficient to make the test case pass with a different endianness, it
is fine with me.

However, I do not understand why it should make a difference.

In general, I do not understand why there is an endian problem. "a" or "1a"
should simply lead to two 4-byte characters. The "int(z'4F60'),4)" should lead
to a single character, which depending on the endianness maps to a different
glyph. All characters should be convertable to UTF-8, which has no endianness
dependence, and convertable back to the original string - which one compares
to.


  parent reply	other threads:[~2014-04-27 11:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 10:20 [Bug libfortran/52539] New: " burnus at gcc dot gnu.org
2012-03-10 14:33 ` [Bug libfortran/52539] " jvdelisle at gcc dot gnu.org
2012-03-10 14:53 ` burnus at gcc dot gnu.org
2014-01-16  8:30 ` dominiq at lps dot ens.fr
2014-03-28 18:52 ` jvdelisle at gcc dot gnu.org
2014-03-28 22:00 ` jvdelisle at gcc dot gnu.org
2014-03-28 23:50 ` jvdelisle at gcc dot gnu.org
2014-04-26 21:57 ` jvdelisle at gcc dot gnu.org
2014-04-27 10:48 ` schwab@linux-m68k.org
2014-04-27 11:14 ` schwab@linux-m68k.org
2014-04-27 11:20 ` schwab@linux-m68k.org
2014-04-27 11:38 ` burnus at gcc dot gnu.org [this message]
2014-04-27 11:59 ` schwab@linux-m68k.org
2014-04-27 12:48 ` burnus at gcc dot gnu.org
2014-04-27 14:56 ` jvdelisle at gcc dot gnu.org
2014-04-27 15:12 ` burnus at gcc dot gnu.org
2014-04-27 17:41 ` jvdelisle at gcc dot gnu.org
2014-05-03  3:31 ` jvdelisle at gcc dot gnu.org
2014-05-03 18:38 ` dominiq at lps dot ens.fr
2014-05-03 18:56 ` jvdelisle at gcc dot gnu.org
2014-05-03 20:48 ` dominiq at lps dot ens.fr
2014-05-05  9:08 ` dominiq at lps dot ens.fr
2014-05-08  4:08 ` jvdelisle at gcc dot gnu.org
2014-05-08  5:18 ` jvdelisle at gcc dot gnu.org
2014-05-18  2:31 ` jvdelisle at gcc dot gnu.org
2014-05-18  2:34 ` jvdelisle at gcc dot gnu.org
2014-05-19  7:05 ` burnus at gcc dot gnu.org
2014-06-07 17:53 ` jvdelisle 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-52539-4-DGgQd71KnF@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).