public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dir at lanl dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32393] gfortran - incorrect run time results
Date: Wed, 20 Jun 2007 14:15:00 -0000 [thread overview]
Message-ID: <20070620141505.14994.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32393-10129@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from dir at lanl dot gov 2007-06-20 14:15 -------
It is easy to make this test case to a completely legal FORTRAN program.
Keeping the BUG and making it into a completely legal FORTRAN program is more
difficult, but likely possible. However, the problem that gfortran is having
with the program is that it does not take the full effect of the "equivalence
(jt,tt)" into account. This is where the real problem is and where I expected
some disagreement. Each line of code in the important loop is legal and the
loop has compiled and run correctly on dozens of FORTRAN compilers with and
without optimization, but one could argue with some justification that the
sequence instructions does something illegal. I will consider it "RESOLVED
INVALID" on that basis.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32393
next prev parent reply other threads:[~2007-06-20 14:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 14:42 [Bug fortran/32393] New: " dir at lanl dot gov
2007-06-18 14:49 ` [Bug fortran/32393] " dir at lanl dot gov
2007-06-18 14:52 ` dominiq at lps dot ens dot fr
2007-06-18 15:05 ` dir at lanl dot gov
2007-06-18 15:29 ` dominiq at lps dot ens dot fr
2007-06-18 16:16 ` burnus at gcc dot gnu dot org
2007-06-18 18:13 ` dir at lanl dot gov
2007-06-18 18:44 ` dominiq at lps dot ens dot fr
2007-06-18 18:46 ` dominiq at lps dot ens dot fr
2007-06-18 21:04 ` burnus at gcc dot gnu dot org
2007-06-19 12:48 ` dominiq at lps dot ens dot fr
2007-06-20 14:15 ` dir at lanl dot gov [this message]
2007-06-20 15:43 ` dominiq at lps dot ens dot fr
2007-06-20 16:21 ` burnus at gcc dot gnu dot org
2007-06-21 12:58 ` dir at lanl dot gov
2007-06-21 13:23 ` dir at lanl dot gov
2007-06-21 16:16 ` dir at lanl dot gov
2007-06-21 16:29 ` dir at lanl dot gov
2007-06-21 16:48 ` burnus at gcc dot gnu dot org
2007-06-21 17:04 ` dominiq at lps dot ens dot fr
2007-06-21 17:14 ` burnus at gcc dot gnu dot org
2007-06-21 20:06 ` dir at lanl dot gov
2007-06-21 20:11 ` dir at lanl dot gov
2007-06-22 9:41 ` burnus at gcc dot gnu dot org
2007-06-22 13:27 ` burnus at gcc dot gnu dot org
2007-06-22 14:28 ` dir at lanl dot gov
2007-06-22 14:32 ` burnus at gcc dot gnu dot org
2007-06-24 10:51 ` dominiq at lps dot ens dot fr
2007-06-24 11:12 ` Andrew Pinski
2007-06-24 11:13 ` pinskia at gmail dot com
2007-06-24 19:28 ` dominiq at lps dot ens dot fr
2007-06-24 19:37 ` Andrew Pinski
2007-06-24 19:37 ` pinskia at gmail dot com
2007-06-24 19:45 ` burnus at gcc dot gnu dot org
2007-06-24 19:52 ` dominiq at lps dot ens dot fr
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=20070620141505.14994.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).