[llvm] [llvm-exegesis] Skip benchmark entries with unknown opcodes in analysis mode (PR #201162)

[Lawson Darrow via llvm-commits]

Lawson-Darrow wrote:




> How easy will it be to add the "did you mean...." helper? I want to make sure that any followup doesn't have to refactor all this code....

This should be easy to add later without refactoring any of this. 

Unknown-opcode diagnostics are produced in one place, YamlContext::getInstrOpcode(), so a "did you mean ...?" helper can compute the closest match from OpcodeNameToOpcodeIdx and append it to the same ErrorStream right there. 

The skip-vs-error machinery (getInputError / readYamls) only decides whether a recorded error is reported to the parser or inspected after the document so it would not need to change.

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