[llvm-branch-commits] [llvm] [CodeGen][NPM] Add a target option to control machine verifier enablement at end of default pipelines (PR #176693)

[Aiden Grossman via llvm-branch-commits]

boomanaiden154 wrote:

> This would mean I would have to make "isMachineVerifierClean()"return false atleast for GCNTargetMachine (currently it does not overload the hook and default returns true). which in turn would disable the expensive build checks currenlty being run for the target. I think we should keep them running while also working towards fixing the issues seen with downstream testing.

If it's not failing in expensive checks with the legacy PM with the verifier enabled, why is it tripping the verifier with the NewPM? That seems to imply an issue with the new pipeline to me.

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