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/66280] [4.8/4.9 Regression] ICE: in vect_get_vec_def_for_operand, at tree-vect-stmts.c:1472
Date: Tue, 16 Jun 2015 12:12:00 -0000 [thread overview]
Message-ID: <bug-66280-4-ZGSDHfjVMK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66280-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66280
--- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Salvatore Filippone from comment #12)
> Created attachment 35763 [details]
> test case
Confirmed - though more like PR66251. This issue seems to be present in
most of the vectorizable_* routines. Ah, no, the strided store support uses
a wrong idiom for getting at vectorized stmts for SLP.
next prev parent reply other threads:[~2015-06-16 12:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-66280-4@http.gcc.gnu.org/bugzilla/>
2015-05-26 10:59 ` [Bug tree-optimization/66280] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-05-29 12:05 ` rguenth at gcc dot gnu.org
2015-05-29 12:30 ` rguenth at gcc dot gnu.org
2015-05-29 12:31 ` rguenth at gcc dot gnu.org
2015-06-01 10:38 ` rguenth at gcc dot gnu.org
2015-06-02 12:35 ` [Bug tree-optimization/66280] [4.8/4.9/5 " rguenth at gcc dot gnu.org
2015-06-03 7:39 ` rguenth at gcc dot gnu.org
2015-06-11 15:24 ` [Bug tree-optimization/66280] [4.8/4.9 " sfilippone at uniroma2 dot it
2015-06-11 15:25 ` sfilippone at uniroma2 dot it
2015-06-16 12:12 ` rguenth at gcc dot gnu.org [this message]
2015-06-16 13:10 ` rguenth at gcc dot gnu.org
2015-06-16 17:31 ` rsandifo at gcc dot gnu.org
2015-06-23 8:24 ` rguenth at gcc dot gnu.org
2015-06-26 20:14 ` [Bug tree-optimization/66280] [4.9 " jakub at gcc dot gnu.org
2015-06-26 20:37 ` jakub 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-66280-4-ZGSDHfjVMK@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).