From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15119 invoked by alias); 20 Jun 2007 14:15:17 -0000 Received: (qmail 14995 invoked by uid 48); 20 Jun 2007 14:15:05 -0000 Date: Wed, 20 Jun 2007 14:15:00 -0000 Message-ID: <20070620141505.14994.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/32393] gfortran - incorrect run time results In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dir at lanl dot gov" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-06/txt/msg01692.txt.bz2 ------- 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