tree 4e6a71fcd04d08df71f601d6e0dade51c2085106
parent 7497689acb7125046625bc78dfb43dc7da9eff38
author Geoffrey Martin-Noble <gcmn@google.com> 1678926454 -0700
committer GitHub <noreply@github.com> 1678926454 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkEmJ2CRBK7hj4Ov3rIwAA4jwIAJmlO7fI/CiorbzbA1Y+DvkU
 aoAczAloQdcEYeWo5Tzbwx4kibptUPGLwKMqHbNg4C8CHtTwI0fOgEuFeK1EO+6K
 CZl0aWIzdnt/T/fK597x5WWR3AV/1KgBAobOfNZeo1cLKWRPpC24QNwlncpxvrv6
 kze8EtvU6FB3shIZfYQpwGndCsg2Je6tZgD+Oz7DoNiAj3SH1FtCXF8GMj/VNP82
 +ILnLN/AGpWE7zSaR1yq9hq2Fe2PCYGtv7WvehXTCutmev9PrcZFNIGZeLD3rfgR
 hiZeERewDI1pd/4OcX4eCSzbUpthjELMTzI11VXnYLUjVwybV4uZK6UAnQgGALs=
 =/36B
 -----END PGP SIGNATURE-----
 

Be consistent about the use of IREE Bazel macros (#12645)

We have some wrapper macros for various rules, mostly to add includes,
but usage was not consistent. This still worked because includes are
inherited transitively, but it only worked by accident basically.

Classifying things this way is also helpful for differentiating compiler
and runtime in bazel query and such (don't need to analyze the whole dep
tree). It could also provide hook points to guard against
cross-component dependencies.