public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Tim Prince" <tprince@computer.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: fortran/4885: BACKSPACE example that doesn't work as of gcc/g77-3.0.x Date: Mon, 05 Nov 2001 02:28:00 -0000 [thread overview] Message-ID: <20011116011603.27644.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR fortran/4885; it has been noted by GNATS. From: "Tim Prince" <tprince@computer.org> To: <toon@moene.indiv.nluug.nl>, <gcc-gnats@gcc.gnu.org> Cc: "Youngjean Jung" <yjjung@newton.berkeley.edu> Subject: Re: fortran/4885: BACKSPACE example that doesn't work as of gcc/g77-3.0.x Date: Thu, 15 Nov 2001 17:12:07 -0800 Doesn't this require ENDFILE 51 before BACKSPACE 51 ? Sure, there have been times when some implementation didn't care. ----- Original Message ----- From: <toon@moene.indiv.nluug.nl> To: <gcc-gnats@gcc.gnu.org> Cc: "Youngjean Jung" <yjjung@newton.berkeley.edu> Sent: Thursday, November 15, 2001 1:10 PM Subject: fortran/4885: BACKSPACE example that doesn't work as of gcc/g77-3.0.x > > >Number: 4885 > >Category: fortran > >Synopsis: BACKSPACE example that doesn't work as of gcc/g77-3.0.x > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: unassigned > >State: open > >Class: sw-bug > >Submitter-Id: net > >Arrival-Date: Thu Nov 15 13:16:01 PST 2001 > >Closed-Date: > >Last-Modified: > >Originator: Youngjean Jung > >Release: 3.0 and higher > >Organization: > >Environment: > Debian GNU/Linux 2.2 > >Description: > The following code: > > open(51,file='s1.dat',status='unknown',access='sequential') > do k=1,100 > call plot(k) > end do > close(51) > end > subroutine plot(k) > j=0 > do i=1,10 > if(j.lt.5) then > j=j+1 > else > backspace 51 > endif > write(51,*) j, k > end do > end > > gives: > > $ ./a.out > $ ./a.out > backspace: end of file > apparent state: unit 51 named s1.dat > last format: list io > lately writing direct formatted external IO > Aborted > > [Note: for the failure to appear, the code has to be run > a second time] > >How-To-Repeat: > > >Fix: > > >Release-Note: > >Audit-Trail: > >Unformatted:
next reply other threads:[~2001-11-16 1:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-11-05 2:28 Tim Prince [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-12-03 15:56 toon 2001-12-03 15:54 toon 2001-11-08 19:26 Toon Moene 2001-11-06 4:46 Youngjean Jung 2001-11-05 16:27 Tim Prince 2001-11-05 15:39 Youngjean Jung 2001-11-05 15:08 Youngjean Jung 2001-11-05 14:11 Toon Moene 2001-11-05 14:01 Youngjean Jung 2001-11-05 2:47 Youngjean Jung 2001-11-05 2:46 Tim Prince 2001-11-05 2:45 Youngjean Jung 2001-11-04 10:56 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=20011116011603.27644.qmail@sourceware.cygnus.com \ --to=tprince@computer.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).