[PATCH] D27826: Regenerate Halide benchmark bitcode files. Resolves TBAA verification failures.

Matthias Braun via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Thu Dec 15 16:52:24 PST 2016

MatzeB added a comment.

In https://reviews.llvm.org/D27826#624321, @sanjoy wrote:

> In https://reviews.llvm.org/D27826#624246, @asbirlea wrote:
> > Yes, they're generated straight from Halide and they pass the verification. I'll update a git mirror shortly as additional reference.
> Given that ^ I'd say they're okay to check in from the perspective of the TBAA verifier.  I have not manually verified the binary files.
> However, I'm not qualified to discuss if this is going to invalidate previous benchmark results and if people need to be notified about that.  What is the normal protocol here?

I am not aware we have any process for this sort of stuff. The usual answer is to try hard not to change the benchmarks in fundamental ways. But this is not the first time such a thing happens and in this specific case we can probably consider the BitCode part as a young emerging part of the test-suite that isn't tracked by that many people yet. I guess Alina knows best who/which bots are tracking the BitCode parts.


More information about the llvm-commits mailing list