public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32218] [4.2/4.3 Regression] segfault with -O1 -ftree-vectorize
Date: Wed, 25 Jul 2007 16:20:00 -0000 [thread overview]
Message-ID: <20070725162016.16251.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32218-12387@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from sje at cup dot hp dot com 2007-07-25 16:20 -------
Well, that was silly. I couldn't reproduce the problem because I had a patch
in my local tree. Here is the patch I created, I will submit it to
gcc-patches.
Basically, get_vectype_for_scalar_type can return a NULL_TREE and we need to
allow for that and not call TYPE_MODE with a NULL_TREE.
Index: tree-vect-patterns.c
===================================================================
--- tree-vect-patterns.c (revision 126897)
+++ tree-vect-patterns.c (working copy)
@@ -651,8 +651,9 @@ vect_pattern_recog_1 (
|| (icode = optab->handlers[(int) vec_mode].insn_code) ==
CODE_FOR_nothing
|| (type_out
- && (insn_data[icode].operand[0].mode !=
- TYPE_MODE (get_vectype_for_scalar_type (type_out)))))
+ && (!get_vectype_for_scalar_type (type_out)
+ || (insn_data[icode].operand[0].mode !=
+ TYPE_MODE (get_vectype_for_scalar_type (type_out))))))
return;
}
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32218
next prev parent reply other threads:[~2007-07-25 16:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 8:31 [Bug tree-optimization/32218] New: " tbm at cyrius dot com
2007-06-06 23:44 ` [Bug target/32218] " sje at cup dot hp dot com
2007-06-30 9:15 ` pinskia at gcc dot gnu dot org
2007-07-01 11:23 ` dorit at gcc dot gnu dot org
2007-07-01 11:32 ` tbm at cyrius dot com
2007-07-01 11:33 ` tbm at cyrius dot com
2007-07-03 20:19 ` sje at cup dot hp dot com
2007-07-04 3:24 ` mmitchel at gcc dot gnu dot org
2007-07-20 3:52 ` mmitchel at gcc dot gnu dot org
2007-07-24 8:53 ` dorit at gcc dot gnu dot org
2007-07-24 18:37 ` tbm at cyrius dot com
2007-07-25 16:20 ` sje at cup dot hp dot com [this message]
2007-07-25 20:24 ` sje at gcc dot gnu dot org
2007-07-26 16:30 ` sje at cup dot hp dot com
2007-07-26 16:38 ` pluto at agmk dot net
2007-07-26 16:44 ` sje at cup dot hp dot com
2007-07-30 15:16 ` sje 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=20070725162016.16251.qmail@sourceware.org \
--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).