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/63341] [4.8/4.9/5 Regression] Vectorization miscompilation with -mcpu=power7
Date: Tue, 23 Sep 2014 11:22:00 -0000 [thread overview]
Message-ID: <bug-63341-4-4L4vJDm4Rc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63341-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63341
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I see non-NULL offset passed to vect_create_data_ref_ptr by vectorizable_store
(for negative case), vectorizable_load (for this
dr_explicit_realign_optimized),
and to vect_create_addr_base_for_vector_ref in vect_gen_niters_for_prolog_loop
(for negative case) and vect_create_cond_for_align_checks (also for negative
case). So guess we'd need to check all these cases what we really want in
those cases.
next prev parent reply other threads:[~2014-09-23 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 11:03 [Bug tree-optimization/63341] New: [4.8/4.9/5 RegressionVectorizer jakub at gcc dot gnu.org
2014-09-23 11:15 ` [Bug tree-optimization/63341] [4.8/4.9/5 Regression] Vectorization miscompilation with -mcpu=power7 jakub at gcc dot gnu.org
2014-09-23 11:22 ` jakub at gcc dot gnu.org [this message]
2014-09-23 11:59 ` rguenth at gcc dot gnu.org
2014-09-23 12:03 ` rguenth at gcc dot gnu.org
2014-09-23 12:08 ` rguenth at gcc dot gnu.org
2014-09-23 12:40 ` jakub at gcc dot gnu.org
2014-09-23 13:37 ` jakub at gcc dot gnu.org
2014-09-25 8:13 ` jakub at gcc dot gnu.org
2014-09-25 8:18 ` jakub at gcc dot gnu.org
2014-09-25 8:19 ` jakub at gcc dot gnu.org
2014-09-25 8:24 ` 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-63341-4-4L4vJDm4Rc@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).