Google Git
Sign in
opensecura / 3p / openxla / iree / 8f5d85f4de36d080f5ad92ad78fe4ee1e1eb3408
commit8f5d85f4de36d080f5ad92ad78fe4ee1e1eb3408[log] [tgz]
authorScott Todd <scotttodd@google.com>Mon Aug 08 15:19:59 2022 -0700
committerGitHub <noreply@github.com>Mon Aug 08 15:19:59 2022 -0700
tree82fe68520a5e30f93637eda2e5c3c9ae92a401ba
parent6b8387ca5c52a477ae6cad500749d8efe008264b [diff]
Tweak Tracy CMake config so release build works again. (#10029)

This fixes the build with `IREE_BUILD_TRACY` on our release Docker image. See a sample failure here: https://github.com/iree-org/iree/actions/runs/2817051970

Tested with `override_python_versions="cp39-cp39" packages="iree-runtime-instrumented" output_dir="/tmp/wheelhouse" ./build_tools/python_deploy/build_linux_packages.sh` before and after.

This check fails:
```
  pkg_check_modules(TRACY_GTK_DEPS
    freetype2
    glfw3
    gtk+-3.0
    dbus-1
  )
```
but we were still building the imgui sources that use `glfw3`:
```
 FAILED: tracy/CMakeFiles/IREETracyIMGUI.dir/__/__/__/third_party/tracy/profiler/src/imgui/imgui_impl_glfw.cpp.o
  /opt/rh/devtoolset-10/root/usr/bin/c++  -I/main_checkout/iree/build_tools/third_party/tracy/../../../third_party/tracy/imgui -I/usr/include/capstone -I/usr/include/capstone/capstone -O3 -DNDEBUG -fPIC -Wno-unused-result -std=gnu++17 -MD -MT tracy/CMakeFiles/IREETracyIMGUI.dir/__/__/__/third_party/tracy/profiler/src/imgui/imgui_impl_glfw.cpp.o -MF tracy/CMakeFiles/IREETracyIMGUI.dir/__/__/__/third_party/tracy/profiler/src/imgui/imgui_impl_glfw.cpp.o.d -o tracy/CMakeFiles/IREETracyIMGUI.dir/__/__/__/third_party/tracy/profiler/src/imgui/imgui_impl_glfw.cpp.o -c /main_checkout/iree/third_party/tracy/profiler/src/imgui/imgui_impl_glfw.cpp
  /main_checkout/iree/third_party/tracy/profiler/src/imgui/imgui_impl_glfw.cpp:73:10: fatal error: GLFW/glfw3.h: No such file or directory
     73 | #include <GLFW/glfw3.h>
        |          ^~~~~~~~~~~~~~
```

---

Separately, I looked into building the Tracy tools on presubmit (like https://github.com/iree-org/iree/pull/9992), but I found that Ubuntu 18.04 includes versions of glfw and zstd that are too old to build Tracy (3.2.1 < 3.3, 1.3.3 < 1.4.0). glfw is just needed for the GUI components, but zstd is necessary for trace compression. We could build those libraries from source rather than install them via apt, but since this is an optional utility in IREE I don't want to jump through those hoops. We could add a new presubmit that uses the release Docker image, or create a newer image based on Ubuntu 20+, if we find ourselves needing this tested on presubmit.
1 file changed
tree: 82fe68520a5e30f93637eda2e5c3c9ae92a401ba
  1. .github/
  2. benchmarks/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazelignore
  15. .bazelrc
  16. .bazelversion
  17. .clang-format
  18. .gitignore
  19. .gitmodules
  20. .pylintrc
  21. .style.yapf
  22. .yamllint.yml
  23. AUTHORS
  24. BUILD.bazel
  25. CITATION.cff
  26. CMakeLists.txt
  27. configure_bazel.py
  28. CONTRIBUTING.md
  29. LICENSE
  30. README.md
  31. 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.

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.

Build Status

CI SystemBuild SystemPlatformArchitectureConfiguration / ComponentStatus
KokoroBazelLinuxx86-64kokoro status bazel/linux/x86-swiftshader/core
KokoroCMake & BazelLinuxx86-64 (swiftshader)Integrationskokoro status cmake-bazel/linux/x86-swiftshader
KokoroCMake & BazelLinuxx86-64 (turing)Integrationskokoro status cmake-bazel/linux/x86-turing
KokoroCMakeLinuxx86-64 (swiftshader)kokoro status cmake/linux/x86-swiftshader
KokoroCMakeLinuxx86-64 (swiftshader)asankokoro status cmake/linux/x86-swiftshader-asan
KokoroCMakeLinuxx86-64 (turing)kokoro status cmake/linux/x86-turing
KokoroCMakeAndroidarm64-v8aRuntime (build only)kokoro status cmake/android/arm64-v8a
KokoroCMakeBare Metalrisc-v-32Runtimekokoro status cmake/baremetal/riscv32
KokoroCMakeLinuxrisc-v-64Runtimekokoro status cmake/linux/riscv64
BuildkiteCMakeAndroidarm64-v8aRuntimebuildkite status iree-android-arm64-v8a
BuildKiteCMakeAndroidarm64-v8aRuntime Benchmarksbuildkite status iree-benchmark
BuildKiteCMakeLinuxx86-64Tracing + Standalone Runtimebuildkite status iree-build-configurations

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

  • 2021-06-09: IREE Runtime Design Tech Talk (recording and slides)
  • 2020-08-20: IREE CodeGen: MLIR Open Design Meeting Presentation (recording and slides)
  • 2020-03-18: Interactive HAL IR Walkthrough (recording)
  • 2020-01-31: End-to-end MLIR Workflow in IREE: MLIR Open Design Meeting Presentation (recording and slides)

License

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