Google Git
Sign in
opensecura / 3p / openxla / iree / 6ff9a3d76caabecffe555e1f38481090e09c2159
commit6ff9a3d76caabecffe555e1f38481090e09c2159[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Fri Mar 01 10:52:00 2024 -0800
committerGitHub <noreply@github.com>Fri Mar 01 18:52:00 2024 +0000
treebfc54b6886ac1eaba7eb4fd677bf1d41c9563d0b
parent7e1ebd8985be1597d9a1c95cdd67e42840b71631 [diff]
Refactor how llvm-cpu check tests interface with ASan/TSan. (#16452)

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

This removes the following CMake options:
* `IREE_BYTECODE_MODULE_FORCE_LLVM_SYSTEM_LINKER`
* `IREE_BYTECODE_MODULE_ENABLE_ASAN`
* `IREE_BYTECODE_MODULE_ENABLE_TSAN`

Now, each test suite using the `llvm-cpu` target will automatically
generate ASan and TSan test cases as well. We don't want to use this
approach for other backends (e.g. CUDA graphs vs streams), but
sanitizers are special in how they interact with the source build.
Future test suite refactoring may further decouple tests from builds
where this should be less complicated.

The `build_tools/cmake/build_and_test_asan.sh` script now also only runs
tests once, shaving a few minutes off of the `asan` CI job.
12 files changed
tree: bfc54b6886ac1eaba7eb4fd677bf1d41c9563d0b
  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.