Displaying 20 results from an estimated 81 matches for "vplans".
Did you mean:
plans
2017 Dec 06
5
[LV][VPlan] Status Update on VPlan ----- where we are currently, and what's ahead of us
Status Update on VPlan ---- where we are currently, and what's ahead of us
==========================================================
Goal:
-----
Extending Loop Vectorizer (LV) such that it can handle outer loops, via uplifting its infrastructure with VPlan.
The goal of this status update is to summarize the progress and the future steps needed.
Background:
-----------
This is related to
2017 Dec 06
3
[RFC][LV][VPlan] Proposal for Outer Loop Vectorization Implementation Plan
Proposal for Outer Loop Vectorization Implementation Plan
=============================================
=====
Goal:
=====
Extending Loop Vectorizer (LV) such that it can handle outer loops, via VPlan infrastructure enhancements.
Understand the trade-offs in trying to make concurrent progress with moving remaining inner loop vectorization
functionality to VPlan infrastructure
===========
2017 Dec 14
3
[RFC][LV][VPlan] Proposal for Outer Loop Vectorization Implementation Plan
>Another might be to introduce changes under feature flags to ease the revert/reintroduce/revert cycle.
This is essentially the first guard. We plan to have flags/settings to control which types of outer loops are handled.
The new code path is initially exclusive to outer loop vectorization. If we disable all types of outer loops
(and that's the initial default), LV continues to be good
2018 Jan 15
0
[RFC][LV][VPlan] Proposal for Outer Loop Vectorization Implementation Plan
To revive the discussion around vectorizer testing, here's a quick
sample of a few of the issues hit recently in the loop vectorizer. I
want to be careful to say that I am not stating these are the result of
any recent work, just that they're issues that have been triaged down to
the loop vectorizer doing something incorrect or questionable from a
performance perspective.
2018 Feb 08
2
[RFC] Make LoopVectorize Aware of SLP Operations
Hi,
On 08/02/2018 04:22, Caballero, Diego wrote:
> Hi Florian!
>
> This proposal sounds pretty exciting! Integrating SLP-aware loop vectorization (or the other way around) and SLP into the VPlan framework is definitely aligned with the long term vision and we would prefer this approach to the LoopReroll and InstCombine alternatives that you mentioned. We prefer a generic implementation
2018 Jun 01
2
[VPlan] Dead instructions are invariant to VFs when build vplan
Hi,
I noticed that the dead instructions collected when build vplan are invariant to different ranges of VFs since the original loop is not changed. Maybe DeadInstructions should be treated as a data member of LoopVectorizationPlanner and initialized by collectTriviallyDeadInstructions() in plan()?
Cheers,
Shixiong (Jason) Xu
-------------- next part --------------
An HTML attachment was
2018 Feb 08
0
[RFC] Make LoopVectorize Aware of SLP Operations
Hi Florian!
This proposal sounds pretty exciting! Integrating SLP-aware loop vectorization (or the other way around) and SLP into the VPlan framework is definitely aligned with the long term vision and we would prefer this approach to the LoopReroll and InstCombine alternatives that you mentioned. We prefer a generic implementation that can handle complicated cases to something ad-hoc for some
2017 Oct 14
3
[RFC] Polly Status and Integration
On Fri, Oct 13, 2017 at 5:13 PM, Michael Kruse via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> 2017-10-14 1:29 GMT+02:00 Saito, Hideki via llvm-dev <
> llvm-dev at lists.llvm.org>:
> > I'm also sorry that I'm not commenting on the main part of your RFC in
> this reply. I just want to focus on
> > one thing here.
> >
> >
2018 Jan 16
1
[RFC][LV][VPlan] Proposal for Outer Loop Vectorization Implementation Plan
On 01/15/2018 03:52 PM, Philip Reames wrote:
> To revive the discussion around vectorizer testing, here's a quick
> sample of a few of the issues hit recently in the loop vectorizer. I
> want to be careful to say that I am not stating these are the result
> of any recent work, just that they're issues that have been triaged
> down to the loop vectorizer doing something
2018 Feb 06
2
[RFC] Make LoopVectorize Aware of SLP Operations
Hello,
We would like to propose making LoopVectorize aware of SLP operations,
to improve the generated code for loops operating on struct fields or
doing complex math.
At the moment, LoopVectorize uses interleaving to vectorize loops that
operate on values loaded/stored from consecutive addresses: vector
loads/stores are generated to combine consecutive loads/stores and then
shufflevector
2020 Jan 11
2
Writing loop transformations on the right representation is more productive
Am Fr., 10. Jan. 2020 um 16:10 Uhr schrieb Renato Golin <rengolin at gmail.com>:
> On Fri, 3 Jan 2020 at 11:27, Michael Kruse via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > 1. Candidate selection through cost function
> > --------------------------------------------
> > Instead of needing to know which transformation is profitable before
> >
2018 Jun 01
2
[VPlan] about vectorization factor selection
Hi,
Current loop vectorizer uses a range of vectorization factors computed by MaxVF. For each VF, it setups unform and scalar info before building VPlan and the final best VF selection. The best VF is also selected within the VF range.
for (unsigned VF = 1; VF <= MaxVF; VF *= 2) {
// Collect Uniform and Scalar instructions after vectorization with VF.
2018 May 28
0
[RFC] A New Divergence Analysis for LLVM
...lues in outer loop
vectorization (opt-in flag -vectorizer-use-da).
o More expressive analysis lattice (uniform/consecutive/strided… +
alignment). This is the full sa lattice (stride+alignment lattice) used
in RV [3].
-- Patch set 3 --
o Templatize the divergence analysis to operate directly on VPlans also
(block/instruction type parametric).
We provide the implementation of this RFC as a fork of LLVM on github
[0]. We welcome your feedback. This implementation will be the source of
upcoming patches.
Thanks,
Simon
[0] VPlan+RV: https://github.com/cdl-saarland/vplan-rv
[1] RV on githu...
2018 Sep 13
4
Loop Distribution pass
Hi,
I found with the help of the optimization remarks a loop that could not
be vectorized, but if loop distribution was enabled this may happen,
which it in fact did with a very significant benchmark improvement (~25%).
I tried (on SystemZ) to enable this pass, and found that it only
affected a handful of files on SPEC. This means I could enable this
without worrying about any regressions on
2019 Sep 18
2
Vectorizing multiple exit loops
On 9/17/2019 3:17 AM, Renato Golin wrote:
> Hi Philip,
>
> Apologies for leaving this thread linger so long. It was in my
> back-burner but Alex's weekly remind me to reply (thanks again,
> Alex!). Starting from the end...
>
> On Mon, 9 Sep 2019 at 18:53, Philip Reames via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> Current Plans
>>
>> At
2018 Sep 13
2
Loop Distribution pass
Jonas/Renato,
>I think it's mostly about the success rate, given it's too conservative. But in the past 2 years, improvements in (and around) the LV have been slowed down a bit due to the move >to VPlan.
It wasn't our intention to slow down LV improvements, but if the project ended up causing other developers take the stance of wait-and-see, that's an inevitable side effect
2017 Oct 13
3
[RFC] Polly Status and Integration
...tedScalarEvolution to make SCEV
modeling possible/simpler/exact.
Used for:
- Assume exact BackedgeTakenCount
- Assume no overflow
Aliasing tracked by AccessAnalysis
G) Transformation
One explicit transformation. Either vectorization is possible or don't
do anything at all.
VPlan: Modifying VPlans (widening, etc) and pick the best according to
the cost model.
H) Code Generation (InnerLoopVectorizer/LoopVersioning)
Create a new vectorized loop (without prologue to get aligned
accesses) and use the old loop as epilogue and if the assumptions are
not met.
VPlan: Generate instructions from t...
2018 Jul 31
3
[RFC][SVE] Supporting SIMD instruction sets with variable vector lengths
On 31 July 2018 at 21:10, David A. Greene via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> writes:
>
>> Hi David,
>>
>> Let me put the last two comments up:
>>
>>> > But we're trying to represent slightly different techniques
>>> > (predication, vscale change) which need
2019 Sep 09
3
Vectorizing multiple exit loops
I've recently mentioned in a few places that I'm interested in enhancing
the loop vectorizer to handle multiple exit loops, and have been asked
to share plans. This email is intended to a) share my current thinking
and b) help spark discussion among interested parties. I do need to
warn that my near term plans for this have been delayed; I got pulled
into an internal project
2018 Mar 20
3
HPC/Parallel/Polly BoF at EuroLLVM
Hey folks,
Do we have proposals for an HPC focused BoF at EuroLLVM?
I'd like to discuss the current efforts around integrating Polly,
parallel IR efforts and vectoriser support in VPlan (like outer loop),
as well as coordination on the next steps around Flang.
--
cheers,
--renato