public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18437] vectorizer failed for matrix multiplication Date: Wed, 27 Jul 2011 12:39:00 -0000 [thread overview] Message-ID: <bug-18437-4-AWlmHWZB65@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-18437-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18437 --- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-07-27 12:38:20 UTC --- The initial testcase is probably a bad example (3x3 matrix). The following testcase is borrowed from Polyhedron rnflow and is vectorized by ICC but not by GCC (the ICC variant is 15% faster): function trs2a2 (j, k, u, d, m) real, dimension (1:m,1:m) :: trs2a2 real, dimension (1:m,1:m) :: u, d integer, intent (in) :: j, k, m real (kind = selected_real_kind (10,50)) :: dtmp trs2a2 = 0.0 do iclw1 = j, k - 1 do iclw2 = j, k - 1 dtmp = 0.0d0 do iclww = j, k - 1 dtmp = dtmp + u (iclw1, iclww) * d (iclww, iclw2) enddo trs2a2 (iclw1, iclw2) = dtmp enddo enddo return end function trs2a2 the reason why GCC cannot vectorize this is that the load from U has a non-constant stride, so vectorization would need to load two scalars and build up a vector (ICC does that). If the stride were constant but not power-of-two GCC would reject that as well, probably to not confuse the interleaving code. Data dependence analysis also rejects non-constant strides. Further complication (for the cost model) is the accumulator of type double compared to the data types of float. ICC uses only half of the float vectors here to handle mixed float/double type loops (but it still unrolls the loop).
next prev parent reply other threads:[~2011-07-27 12:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-18437-4@http.gcc.gnu.org/bugzilla/> 2011-05-22 16:02 ` steven at gcc dot gnu.org 2011-07-27 12:39 ` rguenth at gcc dot gnu.org [this message] 2012-04-17 13:55 ` matz at gcc dot gnu.org 2012-05-09 13:07 ` rguenth at gcc dot gnu.org 2012-07-13 8:50 ` rguenth at gcc dot gnu.org 2023-08-04 20:19 ` pinskia at gcc dot gnu.org 2023-08-04 20:20 ` pinskia at gcc dot gnu.org 2004-11-12 1:22 [Bug tree-optimization/18437] New: " giovannibajo at libero dot it 2004-11-12 2:43 ` [Bug tree-optimization/18437] " pinskia at gcc dot gnu dot org 2005-02-11 19:16 ` pinskia at gcc dot gnu dot org 2005-09-20 17:44 ` pinskia 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-18437-4-AWlmHWZB65@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).