[mlir] support f80 and f128 in parseOptionalType

This seems to have been forgotten when the types were introduced.

Reviewed By: wsmoses

Differential Revision: https://reviews.llvm.org/D120737

Author: ftynse

mlir/lib/Parser/TypeParser.cpp

@@ -34,6 +34,8 @@ OptionalParseResult Parser::parseOptionalType(Type &type) {
   case Token::kw_f16:
   case Token::kw_f32:
   case Token::kw_f64:
+  case Token::kw_f80:
+  case Token::kw_f128:
   case Token::kw_index:
   case Token::kw_none:
   case Token::exclamation_identifier:

mlir/test/IR/parser.mlir

@@ -1420,3 +1420,7 @@ test.dialect_custom_printer custom_format
 // be handled by the dialect.
 // CHECK: test.dialect_custom_format_fallback custom_format_fallback
 test.dialect_custom_format_fallback custom_format_fallback
+
+// Check that an op with an optional result parses f80 as type.
+// CHECK: test.format_optional_result_d_op : f80
+test.format_optional_result_d_op : f80

mlir/test/lib/Dialect/Test/TestOps.td

@@ -1962,6 +1962,12 @@ def FormatOptionalResultCOp : FormatOptionalResultOpBase<"c", [{
   (`:` functional-type($optional, $variadic)^)? attr-dict
 }]>;
 
+def FormatOptionalResultDOp
+  : TEST_Op<"format_optional_result_d_op" > {
+  let results = (outs Optional<F80>:$optional);
+  let assemblyFormat = "(`:` type($optional)^)? attr-dict";
+}
+
 def FormatTwoVariadicOperandsNoBuildableTypeOp
     : TEST_Op<"format_two_variadic_operands_no_buildable_type_op",
               [AttrSizedOperandSegments]> {