[PATCH] D149740: [InlineCost][TargetTransformInfo][AMDGPU] Consider cost of alloca instructions in the caller (1/2)
Juan Manuel Martinez CaamaƱo via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Tue Jun 27 07:21:58 PDT 2023
jmmartinez added inline comments.
================
Comment at: llvm/unittests/Analysis/InlineCostTest.cpp:147
+ 10); // 2*InstCost which defaults to 5 + AllocaCost which defaults to 0
+ ASSERT_EQ(GetFeature(InlineCostFeatureIndex::sroa_losses), 0);
+}
----------------
mtrofin wrote:
> nit: is there something that we can test that's not 0 (to distinguish from "no effect"). Like maybe the total cost?
I think that would make the test fragile, since any change in the way the cost is calculated would break the test despite not changing how the sroa savings/losses are computed.
Would it be good if I add a test for the case where the sroa cost is lost?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D149740/new/
https://reviews.llvm.org/D149740
More information about the llvm-commits
mailing list