[llvm] InlineCost shouldn't assert about zero thresholds when full cost is requested.

[mtrofin]

Summary

When requesting a full cost calculation, threshold values and bonuses could be left 0 without affecting correctness.

llvm/lib/Analysis/InlineCost.cpp

InlineResult CallAnalyzer::analyzeCall(CallBase &Call) {
   assert(NumVectorInstructions == 0);
 
   // Update the threshold based on callsite properties
   updateThreshold(Call, F);
 
   // While Threshold depends on commandline options that can take negative
   // values, we want to enforce the invariant that the computed threshold and
   // bonuses are non-negative.
-  assert(Threshold >= 0);
-  assert(SingleBBBonus >= 0);
-  assert(VectorBonus >= 0);
+  assert(ComputeFullInlineCost || Threshold >= 0);
+  assert(ComputeFullInlineCost || SingleBBBonus >= 0);
+  assert(ComputeFullInlineCost || VectorBonus >= 0);
 
   // Speculatively apply all possible bonuses to Threshold. If cost exceeds
   // this Threshold any time, and cost cannot decrease, we can stop processing
   // the rest of the function body.
   Threshold += (SingleBBBonus + VectorBonus);
 
   // Give out bonuses for the callsite, as the instructions setting them up
   // will be gone after inlining.