[PATCH] D105108: [InstructionCost] Add saturation support.

[Dave Green via Phabricator via llvm-commits]

dmgreen added a comment.

Looking at the documentation of invalid costs, it says

  /// These states can currently be used to indicate whether a cost is valid or
  /// invalid. Examples of an invalid cost might be where the cost is
  /// prohibitively expensive and the user wants to prevent certain
  /// optimizations being performed. Or perhaps the cost is simply unknown
  /// because the operation makes no sense in certain circumstances. These
  /// states can be expanded in future to support other cases if necessary.

Do we have any examples of "Or perhaps the cost is simply unknown because the operation makes no sense in certain circumstances"? Where it wouldn't mean the same as an infinite cost.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D105108/new/

https://reviews.llvm.org/D105108