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 fortran/52251] Nonadvancing I/O and the t edit descriptor
Date: Wed, 15 Feb 2012 07:19:00 -0000	[thread overview]
Message-ID: <bug-52251-4-IRARHb4IWs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52251-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-02-15 07:18:42 UTC ---
Answer: It's a bug in gfortran and sunf95

Bob Corbett wrote:
> I filed an interpretation request on this issue in 1998. [...]
> I suspect that Oracle Solaris Studio Fortran is one of the implementations
> that you saw write "Hello" in column 1.  A defect report was filed against
> Sun Fortran years ago.  I had hoped to fix the problem in the 12.3 release,
> but I ran out of time because I had to work on more important bugs.


The approved interpretation request has the following, cf.
000027 "Sequential formatted I/O: position of the left tab"
at http://j3-fortran.org/doc/year/02/02-006c2.txt :

> QUESTION:
> When a file is positioned within a record at the start of sequential
> formatted I/O, where is the left tab limit (see Section 10.6.1.1)? Is it at
> the start of the record or at the point where the file was positioned at
> the start of execution of the statement?
>
> ANSWER:
> The left tab limit is the point where the file was positioned at the start
> of execution of the statement.
>
> DISCUSSION:
> This follows from the second sentence of 10.6.1.1, which states  "Immediately
> prior to data transfer, the left tab limit becomes defined as the character
> position of the current record."
>
> EDITS: None.


  parent reply	other threads:[~2012-02-15  7:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 20:11 [Bug fortran/52251] New: " burnus at gcc dot gnu.org
2012-02-14 20:30 ` [Bug fortran/52251] " burnus at gcc dot gnu.org
2012-02-15  7:19 ` burnus at gcc dot gnu.org [this message]
2012-02-15 10:11 ` burnus at gcc dot gnu.org
2015-04-23 19:46 ` 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-52251-4-IRARHb4IWs@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).