Google Git
Sign in
opensecura / 3p / openxla / iree / 43f516e2a6a90c5093b709d3b1b41c594a7e0bae
commit43f516e2a6a90c5093b709d3b1b41c594a7e0bae[log] [tgz]
authorScott Todd <scotttodd@google.com>Thu Jan 12 08:31:01 2023 -0800
committerGitHub <noreply@github.com>Thu Jan 12 08:31:01 2023 -0800
treecdafc561197baa5c5eb4623f0bddf9ed4aac3aff
parentb35d4a37e855571af360e109419ede60001a7115 [diff]
Roll forward stateful loop_emscripten changes. (#11801)

This is a roll forward of https://github.com/iree-org/iree/pull/11507

Successful CI run:
https://github.com/iree-org/iree/actions/runs/3897710708/jobs/6655737094

---

I had been testing locally with
[`experimental/web/testing/build_tests.sh`](https://github.com/iree-org/iree/blob/main/experimental/web/testing/build_tests.sh),
which sets `-DCMAKE_BUILD_TYPE=RelWithDebInfo`. The CI uses
[`build_tools/cmake/build_runtime_emscripten.sh`](https://github.com/iree-org/iree/blob/main/build_tools/cmake/build_runtime_emscripten.sh),
which leaves the build type unset and defaults to `Release`.

Release builds were failing with `SyntaxError: Unexpected token
(1:72626)` in `/emsdk/upstream/emscripten/tools/acorn-optimizer.js:1852`
with this code:

![image](https://user-images.githubusercontent.com/4010439/211941096-c2041567-08e7-44bf-b770-ed64b4e76b60.png)

While `for (const [key, value] of Object.entries(object1))` is the
recommended way to iterate through an object's enumerable string-keyed
property key-value pairs
([source](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/entries)),
Emscripten does not appear to support that newer syntax out of the box.
5 files changed
tree: cdafc561197baa5c5eb4623f0bddf9ed4aac3aff
  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. .dockerignore
  19. .gitignore
  20. .gitmodules
  21. .pylintrc
  22. .style.yapf
  23. .yamllint.yml
  24. AUTHORS
  25. BUILD.bazel
  26. CITATION.cff
  27. CMakeLists.txt
  28. configure_bazel.py
  29. CONTRIBUTING.md
  30. LICENSE
  31. README.md
  32. 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

  • 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.