public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31618] [4.2, 4.1 only] backspace intrinsic is not working on an unformatted file
Date: Mon, 23 Apr 2007 19:47:00 -0000 [thread overview]
Message-ID: <20070423194656.26857.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31618-11696@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from tkoenig at gcc dot gnu dot org 2007-04-23 20:46 -------
Fixed on trunk.
Maybe we should backport this once 4.2.1 is open.
--
tkoenig at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |4.2.0 4.1.2
Known to work| |4.3.0
Summary|backspace intrinsic is not |[4.2, 4.1 only] backspace
|working on an unformatted |intrinsic is not working on
|file |an unformatted file
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31618
next prev parent reply other threads:[~2007-04-23 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 10:27 [Bug fortran/31618] New: " Patrick dot Begou at hmg dot inpg dot fr
2007-04-18 14:01 ` [Bug fortran/31618] " jvdelisle at gcc dot gnu dot org
2007-04-19 2:47 ` jvdelisle at gcc dot gnu dot org
2007-04-19 20:35 ` tkoenig at gcc dot gnu dot org
2007-04-20 21:29 ` tkoenig at gcc dot gnu dot org
2007-04-21 22:12 ` tkoenig at gcc dot gnu dot org
2007-04-21 22:47 ` jvdelisle at gcc dot gnu dot org
2007-04-22 21:10 ` patchapp at dberlin dot org
2007-04-23 19:44 ` tkoenig at gcc dot gnu dot org
2007-04-23 19:47 ` tkoenig at gcc dot gnu dot org [this message]
2007-05-20 21:09 ` [Bug fortran/31618] [4.2, 4.1 only] " tkoenig at gcc dot gnu dot org
2007-05-20 21:12 ` tkoenig at gcc dot gnu dot org
2007-05-26 3:14 ` 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=20070423194656.26857.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).