tree 1e17d7424bcb44811799a5f530ffa559a87b95b7
parent 155e91312fe6a612fe8af876cc0330853d89f0f5
author Lei Zhang <antiagainst@google.com> 1622574583 -0400
committer GitHub <noreply@github.com> 1622574583 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgtoX3CRBK7hj4Ov3rIwAAzPkIAA5WomyuofQ3ewkosVyQZwaI
 Of6pqMuqeudmsdgZ7rEVT8N7aLKeaOJne7BYiTYfbXaMf4dD/7jwlRdsLeh1pvfz
 HWCuHHJzbOMXyF67WEqOLUFdxiA+7pNBn0NNpFzshpK4OTJDuWnDMq751PBBmFLP
 GuTGmsx99i+XcgamEdIRWEIw13VJHiSBiIZZl8OH7L6k4yaSByBPFoE/3fC/E4bG
 8fDIlIEXuS0kEnrFaWcFNyBBwxlYA76oo285MjJlYsPB5MmI7aznEMDjps+s7yrg
 keY7HGVWfC+qeTZwZTMwg6u3ToR9Jw/Z1hVZ1k6P7dQtotu53bAVnSWMGgz0JYs=
 =tiMM
 -----END PGP SIGNATURE-----
 

[cmake] Support defining benchmark suites from MLIR input modules (#6024)

We have seen several benchmark artifacts generation issues in
the benchmark pipeline thus far. It's because the benchmark pipeline
is totally detached from the normal CI testing flow and it's not
run pre-submit.

This commit adds a CMake rule, `iree_mlir_benchmark_suite`, to
support defining benchmark suites from MLIR input modules. With it,
we can have benchmark artifact generated by building a normal CMake
target: `cmake --target iree-benchmark-suites`.

Concretely, this rule downloads imported model MLIR files, invokes
`iree-translate` to convert them according to the given translation
flags in the rule, and then generates the corresponding `flagfile`
for `iree-benchmark-module` to use.

With this commit, we should be able to make benchmark artifact
generation a step in the normal CI testing flow. Additionally,
we have the additional benefit that now we have a unified and simple
way for bots and developers to generate the full benchmark suite.

Ideally, we shouldn't be downloading with CMake; we should directly
compile from the initial source (i.e., TensorFlow Python models).
It avoids the manual step for uploading imported model somewhere for
every model we need to benchmark and avoids out-of-date inputs.
But that is tangled with the pending Python testing infrastructure
revamp so we'd prefer to not do that right now.