public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/41711] BOZ format does not support reading large kind reals
Date: Sat, 05 Dec 2009 14:29:00 -0000 [thread overview]
Message-ID: <20091205142922.24169.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41711-10743@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from dominiq at lps dot ens dot fr 2009-12-05 14:29 -------
> According to a note I spotted on clf , reading and writing reals with BOZ is
> invalid, so what we are doing here is an extension.
Do you have a pointer? Also the extension should probably be documented.
> I am tempted to just close this one and do no more.
>
> Any opinions?
On 64 bit platforms, the read can also be fixed by a simple patch like the one
in comment #1 (at some point I have even tested it). Since 64 bit platforms are
becoming the mainstream, I think this fix could be good enough. The dirty
details to implement the read on 32 bit platforms probably do not worth the
required work.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41711
next prev parent reply other threads:[~2009-12-05 14:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 2:59 [Bug libfortran/41711] New: Z format does not support writing KIND=10 reals jvdelisle at gcc dot gnu dot org
2009-10-15 3:14 ` [Bug libfortran/41711] " jvdelisle at gcc dot gnu dot org
2009-10-15 3:15 ` jvdelisle at gcc dot gnu dot org
2009-10-15 3:55 ` kargl at gcc dot gnu dot org
2009-10-15 5:11 ` jvdelisle at gcc dot gnu dot org
2009-10-15 8:48 ` burnus at gcc dot gnu dot org
2009-10-15 9:25 ` dominiq at lps dot ens dot fr
2009-10-16 1:41 ` jvdelisle at gcc dot gnu dot org
2009-10-16 1:58 ` jvdelisle at gcc dot gnu dot org
2009-10-16 8:13 ` dominiq at lps dot ens dot fr
2009-10-29 19:20 ` jvdelisle at gcc dot gnu dot org
2009-10-31 1:49 ` jvdelisle at gcc dot gnu dot org
2009-11-04 0:33 ` [Bug libfortran/41711] BOZ format does not support reading large kind reals jvdelisle at gcc dot gnu dot org
2009-12-05 6:05 ` jvdelisle at gcc dot gnu dot org
2009-12-05 14:29 ` dominiq at lps dot ens dot fr [this message]
2009-12-05 15:01 ` [Bug libfortran/41711] [F2008] " burnus at gcc dot gnu dot org
2009-12-06 1:16 ` kargl at gcc dot gnu dot org
2009-12-07 1:35 ` jvdelisle at gcc dot gnu dot org
2009-12-07 9:23 ` burnus at gcc dot gnu dot org
2009-12-07 9:33 ` burnus at gcc dot gnu dot org
2009-12-07 14:01 ` jvdelisle at gcc dot gnu dot org
2009-12-07 14:43 ` burnus at gcc dot gnu dot org
2009-12-07 14:56 ` dominiq at lps dot ens dot fr
2009-12-07 15:56 ` burnus at gcc dot gnu dot org
2009-12-08 14:12 ` burnus at gcc dot gnu dot org
2009-12-08 14:25 ` [Bug libfortran/41711] [F2008] BOZ edit-descr " burnus at gcc dot gnu dot 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=20091205142922.24169.qmail@sourceware.org \
--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).