From: "H.J. Lu" <hjl.tools@gmail.com>
To: Richard Biener <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR62283
Date: Thu, 30 Apr 2015 03:49:00 -0000 [thread overview]
Message-ID: <CAMe9rOond6qwZHwmn8WfcxVefdOuXpP2dt1HmWZq0ir-vi_J1w@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1504281027040.20496@zhemvz.fhfr.qr>
On Tue, Apr 28, 2015 at 1:29 AM, Richard Biener <rguenther@suse.de> wrote:
>
> The following fixes a missed optimization in basic-block vectorization.
> Currently we require the SLP chain to end up in a sequence of loads
> we support. But of course we can in theory end the SLP chain at
> any point and simply construct the vector operand of the uses by
> pieces. This is what the patch does to handle the case where
> "external" defs are not really external. As the patch is somewhat
> more generic it also handles more cases and relies on the cost model
> to reject the outright non-profitable ones (like the bb-slp-14.c
> case which is run with -fno-vect-cost-model though).
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
>
> Richard.
>
> 2015-04-28 Richard Biener <rguenther@suse.de>
>
> PR tree-optimization/62283
> * tree-vect-slp.c (vect_build_slp_tree): When the SLP build
> fails fatally and we are vectorizing a basic-block simply
> cause the child to be constructed piecewise.
> (vect_analyze_slp_cost_1): Adjust.
> (vect_detect_hybrid_slp_stmts): Likewise.
> (vect_bb_slp_scalar_cost): Likewise.
> (vect_get_constant_vectors): For piecewise constructed
> constants place them after the last def.
> (vect_get_slp_defs): Adjust.
> * tree-vect-stmts.c (vect_is_simple_use): Detect in-BB
> externals for basic-block vectorization.
>
This caused:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65935
--
H.J.
prev parent reply other threads:[~2015-04-30 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 8:32 Richard Biener
2015-04-30 3:49 ` H.J. Lu [this message]
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=CAMe9rOond6qwZHwmn8WfcxVefdOuXpP2dt1HmWZq0ir-vi_J1w@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).