Repository navigation
Release v0.11.1 - #1637
Merged
Merged
Release v0.11.1#1637
Conversation
Member
|
Are these changes upstreamed on ExecuTorch repository or not? Or maybe they have been already applied in upstream ET? |
Contributor
Author
There is a PR with them, I believe not merged yet. |
barhanc
reviewed
Nov 16, 2026
barhanc
left a comment
Member
There was a problem hiding this comment.
Why did you skip to 0.11.2, I'm pretty sure the binaries under 0.11.1 prerelease can be updated / substituted for the new ones.
Member
Sure thing, could you just pin this PR here then? |
7 of 12 tasks
IgorSwat
force-pushed
the
@is/binaries-v0.11.2
branch
from
November 16, 2026 15:51
36b3a66 to
457beb2
Compare
barhanc
approved these changes
Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Points
nativeLibsVersionat v0.11.1-libs.That release was re-published with new Android
coreandvulkanlibraries fromsoftware-mansion-labs/executorch#32 (
7764e753e). That branch contains0a087190, the commit the originalv0.11.1-libs was built from, so nothing from it is lost. No released version pinned v0.11.1-libs (v0.11.0 and the
nightlies pin v0.11.0-libs), so replacing its assets affects no existing install.
What changed
Compared with the original v0.11.1-libs, only the Android core and Vulkan artifacts were replaced:
vulkan-android-{arm64-v8a,x86_64}core-android-{arm64-v8a,x86_64}libexecutorch.sorebuilt from the same commit;executorch.jarunchangedVulkan backend changes:
QK kernel.
tiled kernels, and every Reverb model returned garbage there. Fixed by clamping the index and loading unconditionally.
because its epsilon is subnormal in fp16. The normalisation factor is now computed in fp32. fp32 LayerNorm is
unchanged.
Introduces a breaking change?
Type of change
Tested on
Testing instructions
The benchmark app on a OnePlus 12 (Adreno 750):
yarn bench --platform android --backends vulkan --suite full, with thev0.11.0 libs and with these:
forwardflags in the first run were noise:a 3-repeat recheck came back within noise.
that the original v0.11.1-libs already shipped, not this change.
the OnePlus.
Screenshots
Related issues
PR to the ExecuTorch codebase
Checklist
Additional notes