Remove all `IREE_.*_DISABLE` env checks from .mlir tests. (#16225)

Progress on https://github.com/openxla/iree/issues/16203

This mechanism for filtering inside lit tests
* is a poor match for package-based CI
* has caused some tests to be skipped unintentionally (a test suite is
skipped if _any_ tag is excluded, so including Vulkan _and_ Metal tests
in the same suite results in the suite always being skipped)
* is awkward for developers - running a single lit file to test multiple
backends is an interesting idea, but it requires developers to set these
environment variables instead of filtering at configure time

The `IREE_.*_DISABLE` environment variables are still used as a way to
instruct the various `build_tools/.*/.*test.*.sh` scripts which test
labels to filter. The existing CI jobs use those environment variables
extensively.

Specific changes:

* Drop vulkan/metal and only use vmvx and llvm-cpu in some lit tests 
* Convert some lit tests into check tests
22 files changed
tree: a1d71c6e91b07e2304b8fe528f363c302e9a8a80
  1. .devcontainer/
  2. .github/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. lib/
  9. llvm-external-projects/
  10. runtime/
  11. samples/
  12. tests/
  13. third_party/
  14. tools/
  15. .bazel_to_cmake.cfg.py
  16. .bazelignore
  17. .bazelrc
  18. .bazelversion
  19. .clang-format
  20. .dockerignore
  21. .git-blame-ignore-revs
  22. .gitignore
  23. .gitmodules
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. README.md
  33. WORKSPACE
README.md

IREE: Intermediate Representation Execution Environment

IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.

See our website for project details, user guides, and instructions on building from source.

CI Status IREE Discord Status

Project Status

IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!

Communication Channels

Related Project Channels

  • MLIR topic within LLVM Discourse: IREE is enabled by and heavily relies on MLIR. IREE sometimes is referred to in certain MLIR discussions. Useful if you are also interested in MLIR evolution.

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.