public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56935] Basic block is not SLP-vectorizeed after r197635.
Date: Mon, 15 Apr 2013 14:54:00 -0000	[thread overview]
Message-ID: <bug-56935-4-8utj7oMG1k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56935-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56935

--- Comment #4 from Yuri Rumyantsev <ysrumyan at gmail dot com> 2013-04-15 14:54:50 UTC ---
Richard,

both subq's are accessed the same cash line and it means that after 1st store
tthe 2nd load will stall till finish updating data cash (this is not exact
explanation but if you'd like I can find out more strong and correct definition
of memory conflict). In result non-vectorizable code will run much slower adn
we saw such slowdown on 253.perl from cpu2000.


  parent reply	other threads:[~2013-04-15 14:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 13:58 [Bug tree-optimization/56935] New: " ysrumyan at gmail dot com
2013-04-12 14:01 ` [Bug tree-optimization/56935] " ysrumyan at gmail dot com
2013-04-15 10:27 ` rguenth at gcc dot gnu.org
2013-04-15 14:54 ` ysrumyan at gmail dot com [this message]
2013-04-16  7:48 ` rguenther at suse dot de
2013-04-22 14:47 ` 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-56935-4-8utj7oMG1k@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: link
Be 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).