public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/51751] COMPLEX16 tests fail in Lapack Date: Fri, 06 Jan 2012 13:10:00 -0000 [thread overview] Message-ID: <bug-51751-4-K5zCmd7mGg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51751-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51751 --- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-01-06 13:10:24 UTC --- It works for me with trunk r182883 on powerpc-apple-darwin9: with -O0 --> LAPACK TESTING SUMMARY <-- Processing LAPACK Testing output found in the TESTING direcory SUMMARY nb test run numerical error other error ================ =========== ================= ================ REAL 1070421 38 (0.004%) 0 (0.000%) DOUBLE PRECISION 1052315 203 (0.019%) 0 (0.000%) COMPLEX 508588 2 (0.000%) 0 (0.000%) COMPLEX16 523860 28 (0.005%) 0 (0.000%) --> ALL PRECISIONS 3155184 271 (0.009%) 0 (0.000%) or with -O3 --> LAPACK TESTING SUMMARY <-- Processing LAPACK Testing output found in the TESTING direcory SUMMARY nb test run numerical error other error ================ =========== ================= ================ REAL 1033283 197 (0.019%) 0 (0.000%) DOUBLE PRECISION 1047653 205 (0.020%) 0 (0.000%) COMPLEX 503926 3 (0.001%) 0 (0.000%) COMPLEX16 521520 27 (0.005%) 0 (0.000%) --> ALL PRECISIONS 3106382 432 (0.014%) 0 (0.000%) The main difference with -O3 is --> Testing REAL Singular Value Decomposition [ ssvd.out ] SBD drivers: 32 out of 8360 tests failed to pass the threshold SBD drivers: 32 out of 8360 tests failed to pass the threshold SBD drivers: 32 out of 8360 tests failed to pass the threshold SBD drivers: 32 out of 8360 tests failed to pass the threshold SBD drivers: 32 out of 8360 tests failed to pass the threshold --> Tests passed: 27550 --> Tests failing to pass the threshold: 160 On x86_64-apple-darwin10 with trunk r182460, I got for -O2 or -O3 --> LAPACK TESTING SUMMARY <-- Processing LAPACK Testing output found in the TESTING direcory SUMMARY nb test run numerical error other error ================ =========== ================= ================ REAL 1050655 40 (0.004%) 0 (0.000%) DOUBLE PRECISION 1056977 202 (0.019%) 0 (0.000%) COMPLEX 508588 2 (0.000%) 0 (0.000%) COMPLEX16 530862 28 (0.005%) 0 (0.000%) --> ALL PRECISIONS 3147082 272 (0.009%) 0 (0.000%)
next prev parent reply other threads:[~2012-01-06 13:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-04 12:07 [Bug target/51751] New: " tkoenig at gcc dot gnu.org 2012-01-04 23:18 ` [Bug target/51751] " tkoenig at gcc dot gnu.org 2012-01-06 2:14 ` tkoenig at gcc dot gnu.org 2012-01-06 13:10 ` dominiq at lps dot ens.fr [this message] 2012-01-08 10:13 ` tkoenig at gcc dot gnu.org 2012-01-08 12:29 ` dominiq at lps dot ens.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=bug-51751-4-K5zCmd7mGg@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).