public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/26001] New: LAPACK testsuite failure with optimization Date: Sat, 28 Jan 2006 06:01:00 -0000 [thread overview] Message-ID: <bug-26001-10743@http.gcc.gnu.org/bugzilla/> (raw) The LAPACK testsuite fails with the following error message with -O3 -march=pentium4 -funroll-loops: At line 1162 of file schkee.f Fortran runtime error: Bad integer for item 1 in list input This is not a gfortran frontend problem because LAPACK passes fine without optimization. Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../main/configure --prefix=/home/jerry/gcc/usr --enable-languages=c,fortran --disable-libmudflap Thread model: posix gcc version 4.2.0 20060126 (experimental) I have not tried 4.1 yet. This might be considered critical considering the widespread use of LAPACK. -- Summary: LAPACK testsuite failure with optimization Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: regression AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26001
next reply other threads:[~2006-01-28 6:01 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-28 6:01 jvdelisle at gcc dot gnu dot org [this message] 2006-01-28 7:12 ` [Bug regression/26001] " jvdelisle at gcc dot gnu dot org 2006-01-28 7:13 ` jvdelisle at gcc dot gnu dot org 2006-01-30 18:42 ` kargl at gcc dot gnu dot org 2006-01-30 18:49 ` [Bug fortran/26001] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-01-30 18:52 ` tobi at gcc dot gnu dot org 2006-01-30 18:59 ` [Bug tree-optimization/26001] " pinskia at gcc dot gnu dot org 2006-01-30 19:02 ` pinskia at gcc dot gnu dot org 2006-01-30 19:07 ` tobi at gcc dot gnu dot org 2006-01-30 19:08 ` [Bug middle-end/26001] " pinskia at gcc dot gnu dot org 2006-01-30 19:13 ` pinskia at gcc dot gnu dot org 2006-01-30 19:23 ` [Bug middle-end/26001] [4.1/4.2 Regression] expand uses the wrong part of the string for array accesses tobi at gcc dot gnu dot org 2006-01-30 19:27 ` pinskia at gcc dot gnu dot org 2006-01-30 19:32 ` pinskia at gcc dot gnu dot org 2006-01-30 19:37 ` tobi at gcc dot gnu dot org 2006-01-30 19:39 ` pinskia at gcc dot gnu dot org 2006-01-31 4:56 ` pinskia at gcc dot gnu dot org 2006-01-31 5:19 ` pinskia at gcc dot gnu dot org 2006-01-31 5:33 ` pinskia at gcc dot gnu dot org 2006-01-31 6:39 ` jvdelisle at gcc dot gnu dot org 2006-01-31 14:05 ` pinskia at gcc dot gnu dot org 2006-02-01 1:04 ` [Bug middle-end/26001] [4.1 " pinskia at gcc dot gnu dot org 2006-02-01 1:04 ` [Bug middle-end/26001] [4.1/4.2 " pinskia at gcc dot gnu dot org 2006-02-01 3:09 ` [Bug middle-end/26001] [4.1 " mmitchel at gcc dot gnu dot org 2006-02-03 18:31 ` pinskia at gcc dot gnu dot org 2006-02-03 18:31 ` pinskia at gcc dot gnu dot org 2006-02-04 7:51 ` fengwang 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=bug-26001-10743@http.gcc.gnu.org/bugzilla/ \ --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: 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).