public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/13919] [gfortran] Runtime 'internal error' in IO on i686-pc-linux-gnu only Date: Tue, 03 Feb 2004 16:04:00 -0000 [thread overview] Message-ID: <20040203160411.1951.qmail@sources.redhat.com> (raw) In-Reply-To: <20040129111728.13919.Mart.Rentmeester@sci.kun.nl> ------- Additional Comments From reichelt at gcc dot gnu dot org 2004-02-03 16:04 ------- Confirmed on i686-pc-linux-gnu. Here's a slightly reduced version with hardcoded input filename. Runs fine with g77, but crashes with gfortran. If the input file is empty one gets a segfault instead of the error message. ====================================== program foo integer i open(78,file='data.txt') 1 continue read(78,*,end=2) i write(6,*) i goto 1 2 continue close(78) end ====================================== -- What |Removed |Added ---------------------------------------------------------------------------- CC| |reichelt at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2004-02-03 16:04:11 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13919
next prev parent reply other threads:[~2004-02-03 16:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-29 11:17 [Bug fortran/13919] New: " Mart dot Rentmeester at sci dot kun dot nl 2004-01-29 15:40 ` [Bug libfortran/13919] [gfortran] " pinskia at gcc dot gnu dot org 2004-02-03 16:04 ` reichelt at gcc dot gnu dot org [this message] 2004-02-28 14:53 ` bdavis9659 at comcast dot net 2004-03-24 12:14 ` cvs-commit at gcc dot gnu dot org 2004-03-24 16:01 ` 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=20040203160411.1951.qmail@sources.redhat.com \ --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: 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).