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 libfortran/29627] New: partial unformatted reads shouldn't succeed Date: Sat, 28 Oct 2006 18:10:00 -0000 [thread overview] Message-ID: <bug-29627-10391@http.gcc.gnu.org/bugzilla/> (raw) $ cat partial.f90 program main character(len=1) a(2) open(10, form="unformatted",status="unknown") write (10) 'a' rewind 10 a = 'b' read (10) a print *,a end program main $ gfortran -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../../gcc/trunk/configure --prefix=/home/ig25 --enable-languages=c,fortran Thread model: posix gcc version 4.2.0 20061020 (experimental) This should generate a runtime error. ifort gets this right: $ ifort partial.f90 $ ./a.out forrtl: severe (67): input statement requires too much data, unit 10, file /home/ig25/Krempel/Transfer/fort.10 Image PC Routine Line Source a.out 08085958 Unknown Unknown Unknown a.out 08085450 Unknown Unknown Unknown a.out 08084A0D Unknown Unknown Unknown a.out 080648C8 Unknown Unknown Unknown a.out 08064D6B Unknown Unknown Unknown a.out 08055937 Unknown Unknown Unknown a.out 080554B1 Unknown Unknown Unknown a.out 0804A239 Unknown Unknown Unknown a.out 0804A13C Unknown Unknown Unknown Unknown A7E40EA8 Unknown Unknown Unknown a.out 08049FF1 Unknown Unknown Unknown -- Summary: partial unformatted reads shouldn't succeed Product: gcc Version: 4.2.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tkoenig at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29627
next reply other threads:[~2006-10-28 18:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-28 18:10 tkoenig at gcc dot gnu dot org [this message] 2006-10-28 18:11 ` [Bug libfortran/29627] " tkoenig at gcc dot gnu dot org 2006-10-28 19:30 ` tkoenig at gcc dot gnu dot org 2006-10-28 21:24 ` tkoenig at gcc dot gnu dot org 2006-10-28 23:21 ` jvdelisle at gcc dot gnu dot org 2006-10-29 11:49 ` tkoenig at gcc dot gnu dot org 2006-10-29 11:59 ` tkoenig at gcc dot gnu dot org 2006-10-31 20:58 ` tkoenig at gcc dot gnu dot org 2006-11-01 10:17 ` [Bug libfortran/29627] [4.2/4.1 only] " tkoenig at gcc dot gnu dot org 2006-11-03 11:22 ` tkoenig at gcc dot gnu dot org 2006-11-03 11:30 ` [Bug libfortran/29627] [4.1 " tkoenig at gcc dot gnu dot org 2006-11-04 14:04 ` tkoenig at gcc dot gnu dot org 2006-11-04 14:05 ` tkoenig at gcc dot gnu dot org 2006-11-30 19:26 ` chaoyingfu 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=bug-29627-10391@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: 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).