Remove SwiftShader Docker images and software Vulkan testing. (#15837)

Fixes https://github.com/openxla/iree/issues/15299. This removes
SwiftShader-flavored Dockerfiles from this repository and switches all
uses across the project to use the non-SwiftShader equivalent images.

SwiftShader is a CPU implementation of the Vulkan API which we have been
using for min-spec coverage and testing on devices that lack a physical
GPU. We have CI workflows on most platforms we support that use real
hardware and those builds are reliable enough to drop the
CPU/SwiftShader coverage.

Vulkan tests are still included on presubmit using NVIDIA Tesla T4 GPUs
in the `test_gpu` and `test_tf_integrations_gpu` jobs. Postsubmit jobs
using NVIDIA A100 GPUs and Android phones (pixel-6-pro and
moto-edge-x30) also run Vulkan tests.

Removing these extra Dockerfiles will also help us with the planned
refactoring tracked in https://github.com/openxla/iree/issues/15332.

---

Follow-up work _not_ completed as part of this PR:

- [ ] Add min-spec coverage via profiles
29 files changed
tree: d1681e39d12eb1053bd7535b806c39c85dd81498
  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

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.