[PATCH] D46790: [bugpoint] Actually skip a modules that cause verifier errors

Keno Fischer via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Sat May 12 13:22:43 PDT 2018


loladiro added a comment.

Yeah, I've been thinking about what the best way to test this is. It seems somewhat hard to reliably trigger
a verifier fault by removing an instruction - llvm.stackprotector is the one I see most commonly, but I don't
really want to make the test depend on that behavior. One option is to teach bugpoint to use a custom verifier
pass and then write a custom verifier pass that e.g. checks for the presence of a call. That seems like a decently
attractive option, because it would be a useful feature in its own right. Some frontends have their own invariants
and corresponding verifier passes that they want to maintain in their early passes. Would be nice if bugpoint could
support that. The only thing I'm not quite sure off is to how to do this nicely. Presumably, we could use the analysis
name as a pass and run that through the pass manager. I'm just not sure how to get the analysis result out of that.


Repository:
  rL LLVM

https://reviews.llvm.org/D46790





More information about the llvm-commits mailing list