Google Git
Sign in
opensecura / 3p / openxla / iree / 6d6bd6e86a751611b44ec8c5fab8987cfff97843
commit6d6bd6e86a751611b44ec8c5fab8987cfff97843[log] [tgz]
authorIan Wood <ianwood2024@u.northwestern.edu>Thu Jan 09 11:26:03 2025 -0800
committerGitHub <noreply@github.com>Thu Jan 09 11:26:03 2025 -0800
tree00b321d5aa3b3ccc9352c4f1463182c37e7dbe6c
parentbb1c561cdb25e411071a84cd8173ba107c61c9d3 [diff]
[runtime] Fix runtime tracing compile failure on gcc (#19642)

When compiling with gcc I'm getting an error due to the definition of
`std::atomic<uint32_t> next_tracing_thread_i` having a different
language linkage than the declaration:

```
iree/runtime/src/iree/base/tracing/tracy.cc:468:23: error: conflicting declaration of ‘std::atomic<unsigned int> iree_tracing_context_t::next_tracing_thread_id’ with ‘C’ linkage
```

Strangely, clang seems to be fine with this [godbolt gcc vs
clang](https://godbolt.org/z/Yhfcjhchd).

Signed-off-by: Ian Wood <ianwood2024@u.northwestern.edu>
1 file changed
tree: 00b321d5aa3b3ccc9352c4f1463182c37e7dbe6c
  1. .github/
  2. build_tools/
  3. compiler/
  4. docs/
  5. experimental/
  6. integrations/
  7. lib/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazel_to_cmake.cfg.py
  15. .bazelignore
  16. .bazelrc
  17. .bazelversion
  18. .clang-format
  19. .git-blame-ignore-revs
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .pre-commit-config.yaml
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. MAINTAINERS.md
  33. README.md
  34. RELEASING.md
  35. 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.

IREE Discord Status pre-commit OpenSSF Best Practices

Project news

Project status

Release status

Releases notes are published on GitHub releases.

PackageRelease status
GitHub release (stable)GitHub Release
GitHub release (nightly)GitHub Release
Python iree-base-compilerPyPI version
Python iree-base-runtimePyPI version

Build status

CI PkgCI

Nightly build status

Operating systemBuild status
LinuxCI - Linux arm64 clang
macOSCI - macOS x64 clang
WindowsCI - Windows x64 MSVC

For the full list of workflows see https://iree.dev/developers/general/github-actions/.

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

Community meeting recordings: IREE YouTube channel

DateTitleRecordingSlides
2021-06-09IREE Runtime Design Tech Talkrecordingslides
2020-08-20IREE CodeGen (MLIR Open Design Meeting)recordingslides
2020-03-18Interactive HAL IR Walkthroughrecording
2020-01-31End-to-end MLIR Workflow in IREE (MLIR Open Design Meeting)recordingslides

License

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