Google Git
Sign in
opensecura / 3p / openxla / iree / 315e2387d2cc61baa75f0b3da500e5cc6d4a2378
commit315e2387d2cc61baa75f0b3da500e5cc6d4a2378[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Tue Jan 30 13:35:51 2024 -0800
committerGitHub <noreply@github.com>Tue Jan 30 13:35:51 2024 -0800
treea0986041a6b488ca686aa845352007c07736edd6
parent62fd0d967a138085939f2c7e51f33c14b1725396 [diff]
Allow using iree_lit_test without building the compiler. (#16267)

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

* Install more tools that are used for lit tests
* Import those installed tools
* Filter based on tools existing (imported or built) rather than based
on building the compiler
* Add tests subdirectory _after_ tools are imported/defined

Now I can run more tests from a build that imports compiler tools rather
than build them from source:
```
cmake -G Ninja -B ../iree-build-rt/ . \
  -DIREE_BUILD_COMPILER=OFF \
  -DIREE_HOST_BIN_DIR=D:\dev\projects\iree-build\install\bin \
  -DLLVM_EXTERNAL_LIT=D:\dev\projects\iree\third_party\llvm-project\llvm\utils\lit\lit.py
cmake --build ../iree-build-rt
cmake --build --target iree-test-deps
ctest --test-dir ../iree-build-rt
```

New failures that I see are:

* `iree/tests/e2e/regression/libm_linking.mlir.test`
* WindowsLinkerTool looks for `lld-link`, which we don't install. That
appears to be a copy of `lld`, which is different from IREE's `iree-lld`
(which complains with `Expected -flavor <gnu|link|darwin|wasm>` when I
try to use it in that test)
* `iree/samples/custom_module/dynamic/test/example.mlir.test`
* Not sure what's happening here - this passes in my regular build and
works when run standalone but segfaults when run under ctest in the
installed test suite
7 files changed
tree: a0986041a6b488ca686aa845352007c07736edd6
  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.