public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/31880] silent data corruption in gfortran read statement
Date: Wed, 09 May 2007 23:47:00 -0000 [thread overview]
Message-ID: <20070509234741.6208.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31880-14526@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from kargl at gcc dot gnu dot org 2007-05-10 00:47 -------
(In reply to comment #1)
> Confirmed on i686-linux, for all active branches.
>
I'm not sure how you can confirm this. The program is invalid.
a,b,c, and e are undefined in the write statement, so gfortran
can do whateve it wants.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31880
next prev parent reply other threads:[~2007-05-09 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 15:56 [Bug libfortran/31880] New: " roconnor at health dot usf dot edu
2007-05-09 18:18 ` [Bug libfortran/31880] " fxcoudert at gcc dot gnu dot org
2007-05-09 23:47 ` kargl at gcc dot gnu dot org [this message]
2007-05-10 0:02 ` roconnor2 at tampabay dot rr dot com
2007-05-10 0:07 ` jvdelisle at gcc dot gnu dot org
2007-05-10 1:02 ` jvdelisle at gcc dot gnu dot org
2007-05-10 1:10 ` jvdelisle at gcc dot gnu dot org
2007-05-10 1:14 ` jvdelisle at gcc dot gnu dot org
2007-05-10 3:23 ` jvdelisle at gcc dot gnu dot org
2007-05-10 11:50 ` [Bug libfortran/31880] [4.2 only] " roconnor at health dot usf dot edu
2007-05-10 16:25 ` patchapp at dberlin dot org
2007-05-11 0:35 ` jvdelisle at gcc dot gnu dot org
2007-05-11 18:16 ` tkoenig at gcc dot gnu dot org
2007-05-11 18:20 ` tkoenig at gcc dot gnu dot org
2007-05-11 18:45 ` mark at codesourcery dot com
2007-05-11 21:54 ` jvdelisle at gcc dot gnu dot org
2007-05-11 21:57 ` jvdelisle at gcc dot gnu dot org
2007-05-11 22:01 ` 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=20070509234741.6208.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).