Bump numpy dep up to the 2.0 prerelease. (#16800)

Fixes https://github.com/openxla/iree/issues/16762 and
https://github.com/nod-ai/SHARK-Turbine/issues/530

This fixes compatibility issues between the `iree-runtime` Python
package and numpy 2.0+ (currently in prerelease). If a user installs a
newer numpy version and tries to import IREE, they get an error like
this:

> A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.0.0b1 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled against NumPy 2.0.

The official docs
(https://numpy.org/devdocs/dev/depending_on_numpy.html#numpy-2-0-specific-advice)
have some notes about ways to support both numpy 1.xx _and >= 2.0, but
some (limited) local testing, I _think_ our usage of numpy isn't complex
enough to need anything extra though?

---

Also note: the "base" Dockerfile in IREE (used by some build and test
jobs) bundles these Python build requirements, and I'm not updating the
images in this PR. Our package CI builds are more flexible - they
install frequently changing deps on demand.
2 files changed
tree: 76e9f320766fb30f460f9c7174dfb95b40666d84
  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.