[llvm] [polly] Reapply "[Polly] Update ScopInliner for NPM (#125427)" (PR #164601)

[via llvm-commits]

github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {clang-format}-->


:warning: C/C++ code formatter, clang-format found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
git-clang-format --diff origin/main HEAD --extensions cpp,h -- polly/include/polly/ScopInliner.h llvm/lib/Transforms/Vectorize/VPlanValue.h polly/include/polly/LinkAllPasses.h polly/lib/Support/RegisterPasses.cpp polly/lib/Transform/ScopInliner.cpp --diff_from_common_commit
``````````

:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:

</details>

<details>
<summary>
View the diff from clang-format here.
</summary>

``````````diff
diff --git a/llvm/lib/Transforms/Vectorize/VPlanValue.h b/llvm/lib/Transforms/Vectorize/VPlanValue.h
index a33391e84..83e3fcaae 100644
--- a/llvm/lib/Transforms/Vectorize/VPlanValue.h
+++ b/llvm/lib/Transforms/Vectorize/VPlanValue.h
@@ -41,8 +41,8 @@ class VPRecipeBase;
 class VPInterleaveBase;
 class VPPhiAccessors;
 
-/// This is the base class of the VPlan Def/Use graph, used for modeling the data
-/// flow into, within and out of the VPlan. VPValues can stand for live-ins
+/// This is the base class of the VPlan Def/Use graph, used for modeling the
+/// data flow into, within and out of the VPlan. VPValues can stand for live-ins
 /// coming from the input IR and instructions which VPlan will generate if
 /// executed.
 class LLVM_ABI_FOR_TEST VPValue {

``````````

</details>


https://github.com/llvm/llvm-project/pull/164601