tree 4fcba11e5f19a4ef5357c20231c56a5a071fbb1d
parent 10fd5708d4fd586422cd6d924861311e01516361
author Sandeep Dasgupta <sdasgup@google.com> 1637647541 +0000
committer Copybara-Service <copybara-worker@google.com> 1637648168 -0800

[mlir] Refactoring a few Parser APIs

Refactored two new parser APIs parseGenericOperationAfterOperands and
 parseCustomOperationName out of parseGenericOperation and parseCustomOperation.

Motivation: Sometimes an op can be printed in a special way if certain criteria
is met. While parsing, we need to handle all the versions.
`parseGenericOperationAfterOperands` is handy in situation where we already
parsed the operands and decide to fall back to default parsing.

`parseCustomOperationName` is useful when we need to know details (dialect,
operation name etc.) about a parsed token meant to be an mlir operation.

Reviewed By: rriddle

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

GitOrigin-RevId: e5a8c8c883f1f3f91f40c883dd4f613aca0f7105