tree df37444e6154c5a0aaaf15a8ecb684d9c35ec2d8
parent f1bbc5703cd907133b885e5807a09bd1afd5d3b8
author bjacob <benoitjacob@google.com> 1678217101 -0500
committer GitHub <noreply@github.com> 1678217101 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkB4+NCRBK7hj4Ov3rIwAAJpYIAJKdqxb2xFN75CEWjngFd3bF
 xLyE9IrrlHPMk5oOxZ+WIDfEaTwXBwRF8Xb/RkOIX98iiPl4CL+s5WilmHFTS9KD
 eUJdzsKmUF5OUJhjAmAlNzN2HqnhQfRZG6hCPqIcnOcmOc+lZUD1Ija9swWIcY+H
 YsVDhvp1/zpxNVV+ZNCXuEhBONb5jPOVaNAH0gMHsG9qm0Vcxtl9ONqf7yiLv9Ml
 Ukqz/5NBggftWwsAbhmOTqviwKpPqn86DbROhoWXZPa3UwDNMwGyO05CLdxkkJr7
 lWLIzh7ofhotub0raZ4XUHfBpOo83mMRUvY8EFhbD5ps0AaYKxvfYcr0JXXtnco=
 =+O+J
 -----END PGP SIGNATURE-----
 

Centralize CPU features, fix `iree_cpu_lookup_data_by_key`, add a `iree-cpuinfo` tool (#12498)

The starting point of this PR was that I realized that I had forgotten
to update `iree_cpu_lookup_data_by_key`.

That sent me looking for a way to have it automatically sync'd with the
rest of the code, resulting in the present `.inl` approach.

As a bonus, I added a `iree-cpuinfo` tool, also automatically sync'd
with the `.inl` and just a few lines of impl. This is a quick debugging
tool allowing to answer quickly the question "which CPU features are we
actually detecting on this machine". Obviously the point is not provide
the best CPU feature detection tool, the point is that it's by
construction bug-for-bug equivalent to IREE's actual CPU feature
detection.