From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8187 invoked by alias); 19 Apr 2002 00:26:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 8168 invoked by uid 71); 19 Apr 2002 00:26:01 -0000 Resent-Date: 19 Apr 2002 00:26:01 -0000 Resent-Message-ID: <20020419002601.8167.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-To: nobody@gcc.gnu.org Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, janis187@us.ibm.com Received:(qmail 5286 invoked by uid 61); 19 Apr 2002 00:18:06 -0000 Message-Id:<20020419001806.5285.qmail@sources.redhat.com> Date: Thu, 18 Apr 2002 17:26:00 -0000 From: janis187@us.ibm.com Reply-To: janis187@us.ibm.com To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version:gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: optimization/6368: ia64 bad code for LAPACK with -O2 -funroll-all-loops X-SW-Source: 2002-04/txt/msg00962.txt.bz2 List-Id: >Number: 6368 >Category: optimization >Synopsis: ia64 bad code for LAPACK with -O2 -funroll-all-loops >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Thu Apr 18 17:26:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Janis Johnson >Release: gcc version 3.1 20020418 (prerelease) >Organization: >Environment: ia64-unknown-linux-gnu Itanium, Red Hat Linux release 7.1.94 (Roswell) >Description: LAPACK test output file csb.out reports 120 unexpected failures for ia64-linux when the tests are compiled with -O2 -funroll-all-loops by GCC-3.1-20020418. There are many other failures as well, possibly all related to the one described here. LAPACK takes a couple of hours to build and test on an Itanium system and I haven't yet checked to see if this is a regression from 3.0.4. I can continue to try to come up with a small test case but in the meantime, here's a way to reproduce the problem. If someone looks into this using the full LAPACK distribution, please let me know if my further efforts are not necessary. >How-To-Repeat: Build and test LAPACK as shown by the LAPACK build and test guide (http://gcc.gnu.org/gcc-3.1/testing-lapack.html). Verify that TESTING/csb.out shows no failures. Modify the OPTS line in make.inc to use -O2 -funroll-all-loops and do: cd TESTING/EIG rm chbt21.f make complex cd .. make csb.out This time csb.out will say that 120 out of 540 tests failed to pass the threshold. >Fix: Unknown >Release-Note: >Audit-Trail: >Unformatted: