public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40714] [4.4, 4.5 Regression] Fortran runtime error: Invalid argument
Date: Sat, 11 Jul 2009 15:15:00 -0000 [thread overview]
Message-ID: <20090711151505.19673.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40714-14284@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-07-11 15:15 -------
Marked as regression. Not platform specific. I confirmed this on x86-64
Linux.
We have an illegal seek in transfer.c (next_record_w_unf) at line 2824.
--
jvdelisle at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |4.4.1 4.5.0
Known to work| |4.3.4
Summary|Fortran runtime error: |[4.4, 4.5 Regression]
|Invalid argument |Fortran runtime error:
| |Invalid argument
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40714
next prev parent reply other threads:[~2009-07-11 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 20:48 [Bug fortran/40714] New: " michael dot a dot richmond at nasa dot gov
2009-07-10 21:17 ` [Bug fortran/40714] " dominiq at lps dot ens dot fr
2009-07-11 2:13 ` jvdelisle at gcc dot gnu dot org
2009-07-11 15:15 ` jvdelisle at gcc dot gnu dot org [this message]
2009-07-11 17:16 ` [Bug fortran/40714] [4.4, 4.5 Regression] " jvdelisle at gcc dot gnu dot org
2009-07-15 7:31 ` steven at gcc dot gnu dot org
2009-07-15 7:39 ` burnus at gcc dot gnu dot org
2009-07-15 17:20 ` jb at gcc dot gnu dot org
2009-07-15 21:42 ` jb at gcc dot gnu dot org
2009-07-16 1:31 ` jvdelisle at gcc dot gnu dot org
2009-07-16 3:23 ` jvdelisle at gcc dot gnu dot org
2009-07-17 19:40 ` [Bug fortran/40714] [4.4/4.5 " jb at gcc dot gnu dot org
2009-07-19 23:10 ` jvdelisle at gcc dot gnu dot org
2009-07-19 23:23 ` jvdelisle at gcc dot gnu dot org
2009-07-19 23:26 ` jvdelisle at gcc dot gnu dot org
2009-07-19 23:44 ` jvdelisle 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=20090711151505.19673.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).