public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: janis187@us.ibm.com To: gcc-gnats@gcc.gnu.org Subject: optimization/6368: ia64 bad code for LAPACK with -O2 -funroll-all-loops Date: Thu, 18 Apr 2002 17:26:00 -0000 [thread overview] Message-ID: <20020419001806.5285.qmail@sources.redhat.com> (raw) >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:
next reply other threads:[~2002-04-19 0:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-18 17:26 janis187 [this message] 2002-04-18 18:06 Billinghurst, David (CRTS) 2002-04-21 7:36 Billinghurst, David (CRTS) 2002-10-09 16:55 janis
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=20020419001806.5285.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=gcc-gnats@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).