public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/57037] New: GCC does not generate non-temporal stores on i386 with SSE2+ Date: Mon, 22 Apr 2013 20:29:00 -0000 [thread overview] Message-ID: <bug-57037-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57037 Bug #: 57037 Summary: GCC does not generate non-temporal stores on i386 with SSE2+ Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: anlauf@gmx.de Hello, it appears that gcc does not generate non-temporal stores available on i386 at least with SSE2. This is an important optimization for some memory-bandwidth limited codes. Example: for the stream triad kernel, subroutine stream_kernel_triad (a, b, c, n, s) integer , intent(in) :: n double precision :: a(*), b(*), c(*) double precision, intent(in) :: s integer :: j do j = 1,n a(j) = b(j) + s*c(j) end do end subroutine stream_kernel_triad the Intel compiler generates vectorized code with a throughput that is 25% higher on my Core2 than when disabling the generation of non-temporal stores (i.e. compiling with "-opt-streaming-stores never"). gfortran (using -Ofast -fprefetch-loop-arrays) exactly reproduces the performance of the Intel compiler without temporal stores. It appears that this is an important optimization. Harald
next reply other threads:[~2013-04-22 20:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-22 20:29 anlauf at gmx dot de [this message] 2014-12-29 20:34 ` [Bug target/57037] " anlauf at gmx dot de 2024-04-08 1:28 ` pinskia 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-57037-4@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).