| commit | 3e31d4c5650598351e9976dc3e1f5dc427ce7b45 | [log] [tgz] |
|---|---|---|
| author | Scott Todd <scotttodd@google.com> | Mon Aug 21 11:49:50 2023 -0700 |
| committer | GitHub <noreply@github.com> | Mon Aug 21 11:49:50 2023 -0700 |
| tree | d2856a3e4aa853ce6addd1581437e9b17a8cff0f | |
| parent | 5142828f9d6fb761c98900e45f4e398c6da9af6d [diff] |
Run `build_test_all_windows` on presubmit for relevant changes. (#14747) This CI job is somewhat expensive (cloud $$, time to check out the repo before even building), but I think it makes sense to run on changes that directly modify Windows/MSVC files, similar to how the macos_arm64 build should run on changes to the Metal HAL driver. Note that we already run the `build_test_runtime_windows` job on presubmit for all changes, but that does not exercise the compiler code or e2e tests. That being said, most of our Windows-specific files are runtime code, so we should have relatively good coverage even without this. These are the currently affected files: ``` iree/build_tools/python_deploy/build_windows_packages.ps1 iree/build_tools/python_deploy/install_windows_deps.ps1 iree/compiler/src/iree/compiler/Dialect/HAL/Target/LLVMCPU/internal/WindowsLinkerTool.cpp iree/runtime/src/iree/base/internal/atomics_msvc.h iree/runtime/src/iree/base/internal/dynamic_library_win32.c iree/runtime/src/iree/base/internal/threading_win32.c iree/runtime/src/iree/base/internal/wait_handle_win32.c iree/runtime/src/iree/hal/local/elf/arch/x86_64_msvc.asm iree/runtime/src/iree/hal/local/elf/platform/windows.c iree/runtime/src/iree/task/topology_win32.c ```
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 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!
See our website for more information.
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.