[LLVM] Bump to fb2d6709f (#439) #1730
build_llvm.yml
on: push
Matrix: build
Build llvm-mlir wasm
1h 53m
Matrix: call-build-eudsl / build-eudsl
call-deploy-pip-page
/
deploy
1m 5s
Matrix: call-build-python-bindings / build-mlir-python-bindings
Matrix: call-build-eudsl / release-eudsl
Matrix: call-build-eudsl / test-eudsl-llvmpy
Matrix: call-build-eudsl / test-eudsl-tblgen
call-build-python-bindings
/
...
/
Build eudsl-python-extras sdist
12s
Matrix: call-build-python-bindings / release-mlir-python-bindings
call-build-python-bindings
/
Test mlir-python-bindings wasm
0s
Matrix: call-build-python-bindings / test-mlir-python-bindings
call-build-eudsl
/
...
/
deploy
1m 16s
call-build-python-bindings
/
...
/
Release eudsl-python-extras
9s
Matrix: call-build-python-bindings / call-build-eudsl-python-extras / test-eudsl-python-extras
call-build-python-bindings
/
...
/
deploy
1m 2s
call-build-python-bindings
/
...
/
deploy
1m 25s
Annotations
99 warnings
|
build-llvm-mlir manylinux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/upload-artifact@v4, aminya/setup-cpp@v1, ncipollo/release-action@v1.12.0, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-llvm-mlir manylinux_aarch64:
third_party/llvm-project/llvm/lib/Target/DirectX/DXContainerGlobals.cpp#L342
unused variable 'MMI' [-Wunused-variable]
|
|
build-llvm-mlir manylinux_aarch64
Volume mount /:/ghhost is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
|
|
Build llvm-mlir wasm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, ncipollo/release-action@v1.12.0, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build llvm-mlir wasm
Artifact pattern:*.tar.gz did not match any files
|
|
Build llvm-mlir wasm
Artifact pattern :*.tar.gz did not match any files
|
|
Build llvm-mlir wasm
No files were found with the provided path: llvm-install. No artifacts will be uploaded.
|
|
Build llvm-mlir wasm
'get_temporary_buffer<std::pair<unsigned int, llvm::MDNode *>>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<mlir::OpOperand>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<mlir::detail::ParallelDiagnosticHandlerImpl::ThreadDiagnostic>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<std::pair<const void *, (anonymous namespace)::AliasInitializer::InProgressAliasInfo>>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<const llvm::RuntimeLibcallImpl *>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<llvm::directive::Spelling>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<std::pair<const llvm::Init *, const llvm::Init *>>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<llvm::TrackingStatistic *>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<std::pair<float, llvm::BPFunctionNode *>>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<llvm::BPFunctionNode>' is deprecated [-Wdeprecated-declarations]
|
|
build-llvm-mlir macos_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, ncipollo/release-action@v1.12.0, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-llvm-mlir macos_arm64
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
build-llvm-mlir windows_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, ncipollo/release-action@v1.12.0, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-llvm-mlir manylinux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/upload-artifact@v4, aminya/setup-cpp@v1, ncipollo/release-action@v1.12.0, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-llvm-mlir manylinux_x86_64:
third_party/llvm-project/llvm/lib/Target/DirectX/DXContainerGlobals.cpp#L342
unused variable 'MMI' [-Wunused-variable]
|
|
build-llvm-mlir manylinux_x86_64
Volume mount /:/ghhost is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
|
|
call-deploy-pip-page / deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/configure-pages@v5, actions/deploy-pages@v4, actions/setup-python@v5, actions/upload-artifact@v4, dawidd6/action-download-artifact@v11, geekyeggo/delete-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / Build eudsl windows_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / Build eudsl windows_amd64
cibuildwheel: Invalid skip selector: 'pp*'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
|
|
call-build-eudsl / Build eudsl macos_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / Build eudsl macos_arm64
cibuildwheel: Invalid skip selector: 'pp*'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
|
|
call-build-eudsl / Build eudsl macos_arm64
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
temporary bound to reference member of allocated object will be destroyed at the end of the full-expression [-Wdangling-field]
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
'LLVMStructType' is deprecated: Use of the global context is deprecated, use LLVMStructTypeInContext instead [-Wdeprecated-declarations]
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
cibuildwheel: Invalid skip selector: 'pp*'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
adding 'int' to a string does not append to the string [-Wstring-plus-int]
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
format specifies type 'unsigned int' but the argument has type 'size_t' (aka 'unsigned long') [-Wformat]
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
temporary bound to reference member of allocated object will be destroyed at the end of the full-expression [-Wdangling-field]
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
'LLVMStructType' is deprecated: Use of the global context is deprecated, use LLVMStructTypeInContext instead [-Wdeprecated-declarations]
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
cibuildwheel: Invalid skip selector: 'pp*'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
|
|
call-build-eudsl / Release eudsl ubuntu_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / Release eudsl ubuntu_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / Release eudsl windows_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / Release eudsl macos_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-eudsl / call-deploy-pip-page / deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/configure-pages@v5, actions/deploy-pages@v4, actions/setup-python@v5, actions/upload-artifact@v4, dawidd6/action-download-artifact@v11, geekyeggo/delete-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Build mlir-python-bindings macos_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Build mlir-python-bindings macos_arm64
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_wasm32
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
‘buf’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings windows_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
‘buf’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Build eudsl-python-extras sdist
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Release mlir-python-bindings ubuntu_wasm32
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Release eudsl-python-extras
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Release mlir-python-bindings windows_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Release mlir-python-bindings ubuntu_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Release mlir-python-bindings ubuntu_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / Release mlir-python-bindings macos_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, ncipollo/release-action@v1.12.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / call-deploy-pip-page / deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/configure-pages@v5, actions/deploy-pages@v4, actions/setup-python@v5, actions/upload-artifact@v4, dawidd6/action-download-artifact@v11, geekyeggo/delete-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-build-python-bindings / call-deploy-pip-page / deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/configure-pages@v5, actions/deploy-pages@v4, actions/setup-python@v5, actions/upload-artifact@v4, dawidd6/action-download-artifact@v11, geekyeggo/delete-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
eudsl_ccache_log_macos_arm64
|
369 KB |
sha256:603ff95f332618b8670a9f5c9766779a2fab258a15b272775e039a32325d91f2
|
|
|
eudsl_ccache_log_ubuntu_aarch64
|
156 KB |
sha256:61b2af454eb7233bedaddbd5d9e439876c66e90c9476f2599681d14aebb989d5
|
|
|
eudsl_ccache_log_ubuntu_x86_64
|
84 KB |
sha256:f5116a190ead6284f255407ffa82709464cccaca3974871d82726961a7225a6d
|
|
|
eudsl_ccache_log_windows_amd64
|
194 KB |
sha256:a7724dfb2e2a457d4f87f23427d49f1f2c70b42cdcd7a79aea3101370817957d
|
|
|
eudsl_macos_arm64_artifact
|
87.4 MB |
sha256:03af966483298f3c0e5efef850d19dc0e3ac18c1995cacc4ca052da41844ba83
|
|
|
eudsl_python_extras_sdist_artifact
|
122 KB |
sha256:79153369b40803bd036ca788ae3a79c973014fac010b1cef162c9c634a359491
|
|
|
eudsl_ubuntu_aarch64_artifact
|
105 MB |
sha256:019d975750082a2fec0fce9fead071ce26fe8ae887118bb74374ba7ae22f1d66
|
|
|
eudsl_ubuntu_x86_64_artifact
|
109 MB |
sha256:c2d50a3e14db36cb7133adb98f200fa42730a074e1170bea554eb3bbe4089a41
|
|
|
eudsl_windows_amd64_artifact
|
66.8 MB |
sha256:857e12a99293cbe5809cf3b689940876b26e371c407f3cd370e6d5688325c60c
|
|
|
github-pages
Expired
|
90.4 MB |
sha256:ae5457a8ca10005c2309735953d95f2fad029d7b4467bf7972f69e450b47c7f6
|
|
|
llvm_ccache_log_macos_arm64
|
9.49 MB |
sha256:84944401dcad12ca9bc9b901545095c8dc3673c57f37a635de00bc46b85cc5aa
|
|
|
llvm_ccache_log_manylinux_aarch64
|
4.44 MB |
sha256:5f83732a88999eb7ae1565d015a93603cc5b4c9c5212e993504df6132c5b53b2
|
|
|
llvm_ccache_log_manylinux_x86_64
|
6.09 MB |
sha256:e9e40922b357838c45e1fd07bcdc0ed889e2d1646d2dd190a7d43f355a38aab9
|
|
|
llvm_ccache_log_mlir_wasm32
|
3.13 MB |
sha256:3de35997cc7f9cb8f8a68b0d85481a8db0ae52300e44ba6f3f55d6ab85085095
|
|
|
llvm_ccache_log_windows_amd64
|
8.54 MB |
sha256:d5c1df2582874ea15e14574452a29d9af580d36ac3c9ba1917860613aadf62f5
|
|
|
mlir_macos_arm64_artifact
|
764 MB |
sha256:6bbe14c569170ac8b0e87f2757b13c6ef025caa07845caa5b909f078695a058e
|
|
|
mlir_manylinux_aarch64_artifact
|
785 MB |
sha256:5c52f6c91d2a83d18cce17a6445916e3ea2ada3a8e58ef970897009a123665c1
|
|
|
mlir_manylinux_x86_64_artifact
|
783 MB |
sha256:8331ee9fbb22d9c3e4725151491ebfaf3cc9ebf511f6c446a18ca1724699cbe1
|
|
|
mlir_native_tools_macos_arm64_artifact
|
95.3 MB |
sha256:1a8670178c8b2d760b830a5970bbe85a2c328283c0e9cc2df5dbb684f8f498b8
|
|
|
mlir_native_tools_manylinux_aarch64_artifact
|
108 MB |
sha256:33b403b93d37f0488938d7a47ce3d7e798b5b5be0447c703bf39b0133f4ad0c4
|
|
|
mlir_native_tools_manylinux_x86_64_artifact
|
110 MB |
sha256:4f4ce3f2a762a8dccefa777154b1c917951827957df6b6a95e907af1c83e5579
|
|
|
mlir_native_tools_windows_amd64_artifact
|
66.5 MB |
sha256:5c32e6942ef2246885469bf678149686e30c6be595f5fe835d4f938531ca7b87
|
|
|
mlir_python_bindings_macos_arm64_artifact
|
470 MB |
sha256:e927c4dbfb17d52a8c4c73c8e04593773a655b0270b3df250fdf8bc44e7f2b3a
|
|
|
mlir_python_bindings_ubuntu_aarch64_artifact
|
477 MB |
sha256:1af19c7e7c7c5ab1529730ca7e275b84e2d88cb62ed1800bd8b9b89ada0a880f
|
|
|
mlir_python_bindings_ubuntu_wasm32_artifact
|
35 MB |
sha256:3f190f962be8ac765d061c03b730b2ba858ebf181e850091a1d8135396e79e8c
|
|
|
mlir_python_bindings_ubuntu_x86_64_artifact
|
511 MB |
sha256:68655e719375485965793870e339f1e415ab0bfced03dd5f328b1f6cdb5d5048
|
|
|
mlir_python_bindings_windows_amd64_artifact
|
357 MB |
sha256:80498f730ba3b693d081c356f1343d2cacc7b1a9adc5f5f09ac26d48673d191d
|
|
|
mlir_wheel_macos_arm64_artifact
|
650 MB |
sha256:694abf3109ae1746044d16aafafce01313474a2d3030477af86ecd8de6f63437
|
|
|
mlir_wheel_manylinux_aarch64_artifact
|
671 MB |
sha256:06b09e6f8b87110d2cf24a645264e5b724d072a86d4b18cb9de9408037c24e68
|
|
|
mlir_wheel_manylinux_x86_64_artifact
|
676 MB |
sha256:cb145b47598b3ea1dc8d9186ed6167cfcfe502a12b7dfbe6ea3e3e8fdbc575a5
|
|
|
mlir_wheel_ubuntu_wasm32_artifact
|
190 MB |
sha256:f6b7ad53e641960f8eee448712d53a37bce4e75a0b84b31e2774e6f0b79503a7
|
|
|
mlir_wheel_windows_amd64_artifact
|
478 MB |
sha256:2f33793727e3c48cfe78d2c858dd2071de1c7e90421c1c13d634aff083c11088
|
|
|
mlir_windows_amd64_artifact
|
545 MB |
sha256:3cf2b898820a1eef7db5c60f0ec09d4a71347ef6e4bb9887ffb8e8608d003949
|
|