public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/21621] Inconsistency with binary sequential output Date: Thu, 19 May 2005 16:44:00 -0000 [thread overview] Message-ID: <20050519164401.7028.qmail@sourceware.org> (raw) In-Reply-To: <20050517134432.21621.P.Schaffnit@access.rwth-aachen.de> ------- Additional Comments From tobi at gcc dot gnu dot org 2005-05-19 16:43 ------- Can you be a little more specific on what you're trying to do and why you think that what gfortran does is wrong? I don't think the standard requires sequential access files to be in any reliable format. I find the results surprising, but I'm not yet sure it's a bug. [tobi@marktplatz tests]$ gfortran pr21621.f [tobi@marktplatz tests]$ ./a.out 666.00 13 0.0000 1143373824 8 13 [tobi@marktplatz tests]$ g77 pr21621.f [tobi@marktplatz tests]$ ./a.out 666.00 13 666.00 13 8 8 [tobi@marktplatz tests]$ -- What |Removed |Added ---------------------------------------------------------------------------- CC| |tobi at gcc dot gnu dot org Status|UNCONFIRMED |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2005-05-19 16:43:58 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21621
next prev parent reply other threads:[~2005-05-19 16:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-17 13:49 [Bug libfortran/21621] New: " P dot Schaffnit at access dot rwth-aachen dot de 2005-05-17 17:31 ` [Bug libfortran/21621] " pinskia at gcc dot gnu dot org 2005-05-19 16:44 ` tobi at gcc dot gnu dot org [this message] 2005-05-19 16:45 ` tobi at gcc dot gnu dot org 2005-05-23 9:06 ` P dot Schaffnit at access dot rwth-aachen dot de 2005-05-24 20:33 ` jblomqvi at cc dot hut dot fi 2005-05-31 2:37 ` bdavis9659 at comcast dot net 2005-05-31 2:45 ` pinskia 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=20050519164401.7028.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: 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).