public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: arends@nlr.nl
To: gcc-gnats@gcc.gnu.org
Cc: merazzi@smr.ch
Subject: fortran/4722: f77 0.5.26 handles EOF in scratch files incorrectly, f77 0.5.25 is OK
Date: Sun, 28 Oct 2001 12:56:00 -0000	[thread overview]
Message-ID: <20011028205109.12568.qmail@sourceware.cygnus.com> (raw)

>Number:         4722
>Category:       fortran
>Synopsis:       f77 0.5.26 handles EOF in scratch files incorrectly, f77 0.5.25 is OK
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Oct 28 12:56:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Paul Arendsen
>Release:        unknown-1.0
>Organization:
>Environment:
Linux IA32 (RedHat 7.1)
>Description:
f77 0.5.26 is used in Redhat 7.1 incorrectly handles scratch 
files, while it is being treated OK using f77 0.5.25 as in 
SuSe 7.2. The incorrect handling occurs when the end of file
(EOF) is reached.

Compile attached file " g77 tt.f -o tt.x"
run tt.x and and should get
1
2
3
end of file

The 0.5.26 version gives
1
2
3
error in file


Hence incorrect handling when the end of file
has been reached. For me developing Finite Element
software (mostly Fortran and some C) this is 
quite unpleasant.
>How-To-Repeat:
Compile and run attached file one should get
1
2
3
end of file
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="tt.f"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="tt.f"

YzIzNDU2NwogICAgICBwcm9ncmFtIHR0CiAgICAgIGludGVnZXIgaQogCiAgICAgIG9wZW4gKDEs
YWNjZXNzPSdzZXF1ZW50aWFsJyxmb3JtPSd1bmZvcm1hdHRlZCcsCiAgICAgKiAgICAgICBzdGF0
dXM9J3NjcmF0Y2gnKQogCiAgICAgIGRvIGk9MSwzCiAgICAgIHdyaXRlKDEpIGkKICAgICAgZW5k
ZG8KICAgICAgcmV3aW5kICgxKQogCjEwICAgIHJlYWQoMSxlcnI9OTAwLGVuZD04MDApIGkKNTAg
ICAgZm9ybWF0KGkzKQogICAgICBwcmludCosaQogICAgICBnb3RvIDEwCiAKODAwICAgY29udGlu
dWUKICAgICAgcHJpbnQqLCJlbmQgb2YgZmlsZSIKICAgICAgZ290byAxMDAwCiAKOTAwICAgY29u
dGludWUKICAgICAgcHJpbnQqLCJlcnJvciBpbiBmaWxlIgogCjEwMDAgIGNvbnRpbnVlCiAgICAg
IGVuZAo=


             reply	other threads:[~2001-10-28 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-28 12:56 arends [this message]
2001-10-29  7:10 toon

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=20011028205109.12568.qmail@sourceware.cygnus.com \
    --to=arends@nlr.nl \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=merazzi@smr.ch \
    /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).