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/59006] [4.9 Regression] internal compiler error: in vect_transform_stmt, at tree-vect-stmts.c:5963
Date: Tue, 19 Nov 2013 13:51:00 -0000	[thread overview]
Message-ID: <bug-59006-4-9RtZBUBelv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59006-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |congh at gcc dot gnu.org

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
  if (!vect_is_simple_cond (cond_expr, stmt, loop_vinfo, bb_vinfo,
                            &comp_vectype)
      || !comp_vectype)
    return false;

fails during transform.  This is because we moved the invariant load
and thus the vect_def_type changed from vect_internal_def to vect_external_def.

Bah, I knew this is going to be a problem ... the invariant moving should
have been done when vectorizing the stmt, not upfront.  And the moving
should have only moved the vectorized variant.

I'm trying to fix it in another way that is on my TODO list for some time now.


  parent reply	other threads:[~2013-11-19 13:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 14:30 [Bug c/59006] New: " regehr at cs dot utah.edu
2013-11-06 16:06 ` [Bug c/59006] " regehr at cs dot utah.edu
2013-11-06 17:24 ` [Bug tree-optimization/59006] [4.9 Regression] " mpolacek at gcc dot gnu.org
2013-11-19 13:51 ` rguenth at gcc dot gnu.org [this message]
2013-11-19 14:17 ` rguenth at gcc dot gnu.org
2013-11-20  2:05 ` congh at google dot com
2013-11-20  9:10 ` rguenther at suse dot de
2014-01-14  9:05 ` rguenth at gcc dot gnu.org
2014-01-14  9:06 ` 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-59006-4-9RtZBUBelv@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).