public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46172] [4.3/4.4/4.5/4.6 Regression] ICE: in expand_widen_pattern_expr, at optabs.c:522 with -ftree-vectorize -fno-tree-dce
Date: Tue, 02 Nov 2010 12:39:00 -0000	[thread overview]
Message-ID: <20101102123900._iubH3uKhPMiKoaN6yEL2-a4iel4_bbYjMT_MWZQ7js@z> (raw)
In-Reply-To: <bug-46172-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
         AssignedTo|jakub at gcc dot gnu.org    |unassigned at gcc dot
                   |                            |gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-11-02 12:39:16 UTC ---
The problem is that we create DOT_PLUS_EXPR in vect_recog_dot_prod_pattern and
it is kept, because for vector mode the pattern is supported, but then it is
kept also for the final loop handling last few entries and for scalar modes
there is no sdot_prod* pattern.

During expansion DOT_PROD_EXPR is expanded using expand_widen_pattern_expr
which ICEs if there is no handler for it.

To fix this, either the vectorizer would need to undo DOT_PROD_EXPR in the
scalar code if there is no DOT_PROD_EXPR scalar handler, or expansion should
check if there is a handler for it and if not, expand it manually using
multiplication and addition, or all the 3 targets that have
sdot_prod*/udot_prod* patterns should always support both vector and scalar
patterns.


  parent reply	other threads:[~2010-11-02 12:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 21:17 [Bug tree-optimization/46172] New: " zsojka at seznam dot cz
2010-10-26  7:12 ` [Bug tree-optimization/46172] [4.2/4.3/4.4/4.5/4.6 Regression] " hjl.tools at gmail dot com
2010-10-26  8:21 ` hjl.tools at gmail dot com
2010-10-26 14:01 ` [Bug tree-optimization/46172] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu.org
2010-11-02  9:47 ` jakub at gcc dot gnu.org
2010-11-02 12:39 ` jakub at gcc dot gnu.org [this message]
2010-11-02 13:12 ` irar at il dot ibm.com
2010-11-02 13:19 ` jakub at gcc dot gnu.org
2010-11-02 13:28 ` irar at il dot ibm.com
2010-11-02 15:21 ` jakub at gcc dot gnu.org
2010-11-03 11:19 ` jakub at gcc dot gnu.org
2010-11-12 14:46 ` rguenth at gcc dot gnu.org
2010-11-18 15:18 ` rguenth at gcc dot gnu.org
2010-11-18 15:27 ` 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=20101102123900._iubH3uKhPMiKoaN6yEL2-a4iel4_bbYjMT_MWZQ7js@z \
    --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).