Displaying 20 results from an estimated 6000 matches similar to: "LoopStrengthReduce Code Owner: nominating Quentin"
2016 Nov 18
0
LoopStrengthReduce Code Owner: nominating Quentin
> On Nov 17, 2016, at 8:51 PM, Andrew Trick via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> I’d like to nominate Quentin Colombet as LSR code owner. He has handled most of the reviews for me for the past couple years (thanks Quentin), and is willing to take on the responsiblity. Frankly, turning over ownership to Quentin is overdue.
This also seems pretty obvious to me, and
2015 Aug 18
2
RFC for a design change in LoopStrengthReduce / ScalarEvolution
> Of course, and the point is that, for example, on x86_64, the zext here is free. I'm still trying to understand the problem...
>
> In the example you provided in your previous e-mail, we choose the solution:
>
> `GEP @Global, zext(V)` -> `GEP (@Global + zext VStart), {i64 0,+,1}`
> `V` -> `trunc({i64 0,+,1}) + VStart`
>
> instead of the actually-better
2015 Aug 17
2
RFC for a design change in LoopStrengthReduce / ScalarEvolution
> To back up for a second, how much of this is self-inflicted damage?
> IndVarSimplify likes to preemptively widen induction variables. Is
> that why you have the extensions here in the first place?
In the specific example I was talking about the zext came from our
frontend (our FE used to insert these extensions for reasons that are
no longer relevant). But you can easily get the same
2015 Aug 17
2
RFC for a design change in LoopStrengthReduce / ScalarEvolution
This is related to an issue in loop strength reduction [1] that I've
been trying to fix on and off for a while. [1] has a more detailed
description of the issue and an example, but briefly put, I want LSR
to consider formulae that have "Zext T" as base and/or scale
registers, and to appropriately rate such formulae.
My first attempt[2] at fixing this was buggy and had to be
2015 Aug 17
4
RFC for a design change in LoopStrengthReduce / ScalarEvolution
> I don't understand why you want to factor out the information,
> exactly. It seems like what you need is a function like:
>
> unsigned getMinLeadingZeros(const SCEV *);
>
> then, if you want to get the non-extended expression, you can just
> apply an appropriate truncation. I assume, however, that I'm missing
> something.
The problem is not about how to codegen
2017 Jul 06
3
LLVM's loop strength reduction module
Hi Raghavan,
I concur no specific docs.
What do you want to know specifically?
Cheers,
-Quentin
> On Jul 5, 2017, at 11:16 PM, Madhur Amilkanthwar via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> AFAIK, no official doc.
> You can probably get better help if you ask specific questions (which part of the code you don't understand).
>
> On Thu, Jul 6, 2017 at 9:53
2017 Jul 31
1
LLVM's loop strength reduction module
Hi,
Sorry I took a long time to reply as it took me some time to get some understanding of the code even to ask some specific questions (I have a test case in which LSR does not kick in and wanted to understand the code to figure out why it was not kicking in).
Here are some specific questions I have:
1) It appears that LSR works only for the inner-most loop. Is this correct? Can you tell
2016 Mar 28
2
LoopStrengthReduce.cpp
Hi,
I am looking for a way to rewrite induction variables to use an addition
of -1 whenever possible (and not otherwise unprofitable). This is needed
to utilize hardware loop instructions, which are present on SystemZ
(branch on count). Later in the backend, an 'add -1; compare w/ 0; jne
0'-sequence can be replaced with a brct instruction.
I could not find any way in the LSR pass to
2016 Mar 29
0
LoopStrengthReduce.cpp
On 3/29/2016 3:05 AM, Jonas Paulsson via llvm-dev wrote:
> Could this be done somehow, or is it really so that all targets have to
> have their own passes to do this?
In the Hexagon backend we also have a separate pass that converts
compare+branch loops into hardware loops. We recognize several
different patterns of the controlling induction variable, including
cases where the increment
2016 Mar 31
1
LoopStrengthReduce.cpp
> On that note, I think that in general it would be useful to have some
> target-independent (CodeGen) pass that would do the majority of the
> work for hardware loop generation. I have thought about it, but I
> won't be able to do anything in the short term.
>
> -Krzysztof
>
I think a first and useful step would be to let targets optionally have
the loop induction
2016 Mar 29
0
LoopStrengthReduce.cpp
Hi Jonas,
Are you talking specifically about the induction variable? You might look at what I did for PowerPC's counter-based loops (lib/Target/PowerPC/PPCCTRLoops.cpp, etc.).
-Hal
----- Original Message -----
> From: "Jonas Paulsson via llvm-dev" <llvm-dev at lists.llvm.org>
> To: "llvm-dev" <llvm-dev at lists.llvm.org>
> Sent: Monday, March 28,
2016 Mar 24
0
LSR/SCEV problem/question
Hi Geoff,
Firstly, I think it will be great if you have a small reproducer of
this issue (which I can make fail after re-applying D18001 to ToT).
> I’ve run into what appears to be a bug in ScalarEvolution, but I’m not sure
> if it is instead caused by me missing an implicit assumption between LSR and
> SCEV.
>
> This issue is caused by the change D18001, which is an attempt to
2015 Oct 22
7
Nominating Tim Northover as new ARM target code owner
Hi all,
I’d like to nominate Tim Northover to take over code ownership of ARM target.
Thanks,
Evan
2013 Jan 21
2
[LLVMdev] [llvm-commits] [llvm] r172534 - /llvm/trunk/test/Transforms/LoopStrengthReduce/post-inc-icmpzero.ll
On Jan 21, 2013, at 12:37 PM, Chandler Carruth <chandlerc at google.com> wrote:
> On Mon, Jan 21, 2013 at 11:49 AM, Andrew Trick <atrick at apple.com> wrote:
> Moving to llvmdev...
>
> On Jan 21, 2013, at 11:37 AM, Nadav Rotem <nrotem at apple.com> wrote:
>
> > Hi Manish,
> >
> > Thank you for looking at this. Recently opt started using the
2016 Mar 29
2
LoopStrengthReduce.cpp
Hi Hal,
yes, it's all about the induction variable. SystemZ has a late pass
(pre-emit) that looks for MI sequences that can be rewritten to 'branch
on count'. Currently only about half the number of BRCTs are output
compared to gcc on the same benchmarks. One reason for this is that when
a loop gets unrolled, the loop gets a greater increment / decrement than
1, which makes the
2016 Mar 23
6
LSR/SCEV problem/question
Hi All,
I've run into what appears to be a bug in ScalarEvolution, but I'm not sure
if it is instead caused by me missing an implicit assumption between LSR and
SCEV.
This issue is caused by the change D18001 <http://reviews.llvm.org/D18001> ,
which is an attempt to increase SCEV-inserted instruction re-use by picking
a more canonical insertion position in the case where a new
2013 Jan 21
1
[LLVMdev] [llvm-commits] [llvm] r172534 - /llvm/trunk/test/Transforms/LoopStrengthReduce/post-inc-icmpzero.ll
On Jan 21, 2013, at 3:12 PM, Chandler Carruth <chandlerc at google.com> wrote:
> On Mon, Jan 21, 2013 at 2:59 PM, Andrew Trick <atrick at apple.com> wrote:
>
> On Jan 21, 2013, at 12:37 PM, Chandler Carruth <chandlerc at google.com> wrote:
>
>> On Mon, Jan 21, 2013 at 11:49 AM, Andrew Trick <atrick at apple.com> wrote:
>> Moving to llvmdev...
2013 Jan 21
2
[LLVMdev] [llvm-commits] [llvm] r172534 - /llvm/trunk/test/Transforms/LoopStrengthReduce/post-inc-icmpzero.ll
Moving to llvmdev...
On Jan 21, 2013, at 11:37 AM, Nadav Rotem <nrotem at apple.com> wrote:
> Hi Manish,
>
> Thank you for looking at this. Recently opt started using the "-mtriple" command line flag to initialize the TargetMachine for IR-level transformations that use it. Currently only the following passes are using this feature: LSR, LowerSwitch, BBVectorizer and
2013 Jan 21
0
[LLVMdev] [llvm-commits] [llvm] r172534 - /llvm/trunk/test/Transforms/LoopStrengthReduce/post-inc-icmpzero.ll
Moving to llvm-dev...
On Jan 21, 2013, at 9:07 AM, Manish Verma <manish.verma at arm.com> wrote:
> Hi Andy,
>
> I have been able track down the reason for the difference in output
> generated by
> opt. The difference is caused when the target triple specified in the
> test-case
> is not a supported target for opt/clang/llvm. In this case, opt doesn't thow
> an
2013 Jan 21
0
[LLVMdev] [llvm-commits] [llvm] r172534 - /llvm/trunk/test/Transforms/LoopStrengthReduce/post-inc-icmpzero.ll
On Mon, Jan 21, 2013 at 11:49 AM, Andrew Trick <atrick at apple.com> wrote:
> Moving to llvmdev...
>
> On Jan 21, 2013, at 11:37 AM, Nadav Rotem <nrotem at apple.com> wrote:
>
> > Hi Manish,
> >
> > Thank you for looking at this. Recently opt started using the "-mtriple"
> command line flag to initialize the TargetMachine for IR-level
>