[llvm] [mlir] [mlir][tosa] Remove availability interfaces from profile conformance (PR #207809)

[Luke Hutton via llvm-commits]

================
@@ -508,22 +484,18 @@ LogicalResult TosaProfileCompliance::checkProfileOrExtension(
   const TosaSpecificationVersion targetVersion{targetEnv.getSpecVersion()};
   const auto isVersionCompatible =
       [&targetVersion](const OpComplianceInfo<T> &info) -> bool {
+    // Assume compatible if there are no versioned type constraints
+    if (info.operandTypeInfoSet.empty())
----------------
lhutton1 wrote:

Typically when an op is added, it either has data type constraints, or it is added along with a new extension, both of which are checked against the specification version. 

You're correct though, there is a gap here if a new operator is added and it doesn't have type constraints and the profile/extension it is added to isn't new. We've not encountered this scenario yet, but we should be able to do so by extending the profile conformance table with versioning per operator when we encounter it.

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