public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Joost.VandeVondele at pci dot uzh.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/47298] -O3 destroys beautifully vectorized code obtained at -O2 Date: Fri, 14 Jan 2011 21:11:00 -0000 [thread overview] Message-ID: <bug-47298-4-aIuLlC2TuM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47298-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47298 --- Comment #2 from Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> 2011-01-14 20:52:54 UTC --- (In reply to comment #1) > It's faster for me with -O3 (Athlon64, using -march=native). well not on model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 5 I have 8Gflops with -O2 and somewhat more than 4 with -O3 BTW, the proper test program is > cat test_compare.f90 REAL(KIND=8), DIMENSION(12,12) :: A,B,C A=0 ; B=0 ; C=0 DO I=1,10000000 CALL HARD_NN_12_12_12(C,A,B) ENDDO END
next prev parent reply other threads:[~2011-01-14 20:53 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-14 20:53 [Bug middle-end/47298] New: " Joost.VandeVondele at pci dot uzh.ch 2011-01-14 21:02 ` [Bug middle-end/47298] " rguenth at gcc dot gnu.org 2011-01-14 21:11 ` Joost.VandeVondele at pci dot uzh.ch [this message] 2011-01-14 21:27 ` Joost.VandeVondele at pci dot uzh.ch 2012-06-29 14:44 ` Joost.VandeVondele at mat dot ethz.ch 2012-06-29 15:01 ` rguenth at gcc dot gnu.org 2012-07-05 7:36 ` ebotcazou at gcc dot gnu.org 2012-07-05 8:38 ` rguenth at gcc dot gnu.org 2012-07-05 8:48 ` ebotcazou at gcc dot gnu.org 2012-07-05 10:10 ` rguenth at gcc dot gnu.org 2012-07-05 10:12 ` rguenth at gcc dot gnu.org 2012-07-05 10:30 ` ebotcazou at gcc dot gnu.org 2013-03-27 13:02 ` rguenth at gcc dot gnu.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-47298-4-aIuLlC2TuM@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).