Shixiong Xu via llvm-dev
2018-Jun-01 09:56 UTC
[llvm-dev] [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 scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180601/69f28841/attachment.html>
Florian Hahn via llvm-dev
2018-Jun-01 10:21 UTC
[llvm-dev] [VPlan] Dead instructions are invariant to VFs when build vplan
Hi On 01/06/2018 10:56, Shixiong Xu via llvm-dev wrote:> 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()? >Yep you are right. There's a patch under review, which also addresses that: https://reviews.llvm.org/D47477 Thanks, Florian
Shixiong Xu via llvm-dev
2018-Jun-01 11:09 UTC
[llvm-dev] [VPlan] Dead instructions are invariant to VFs when build vplan
Thanks. I didn't notice the patch. 😊 Shixiong -----Original Message----- From: Florian Hahn <florian.hahn at arm.com> Sent: Friday, June 01, 2018 11:21 AM To: Shixiong Xu <shixiong at cadence.com>; llvm-dev at lists.llvm.org Cc: Caballero, Diego <diego.caballero at intel.com>; nd <nd at arm.com> Subject: Re: [llvm-dev] [VPlan] Dead instructions are invariant to VFs when build vplan EXTERNAL MAIL Hi On 01/06/2018 10:56, Shixiong Xu via llvm-dev wrote:> 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()? >Yep you are right. There's a patch under review, which also addresses that: https://urldefense.proofpoint.com/v2/url?u=https-3A__reviews.llvm.org_D47477&d=DwIC-g&c=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY&r=FZEW1cDCyCU3ZbRFatG9st_R0bbu9fLOaIEKyKAe7wg&m=1H53Xvb7phmsnD0jJKQxe1-wa0mbdewKcT8B8DbRzYk&s=GtJno4-QfCaG0-yzw_SCrQ65uTZXwWVuWUL72Y_ySGc&e Thanks, Florian
Maybe Matching Threads
- [VPlan] about vectorization factor selection
- Cost model is missing in InstCombiner
- Cost model is missing in InstCombiner
- [LV][VPlan] Status Update on VPlan ----- where we are currently, and what's ahead of us
- [RFC][LV][VPlan] Proposal for Outer Loop Vectorization Implementation Plan