This is an automated email from the ASF dual-hosted git repository.
expye pushed a change to branch flashinfer-submodule-upgrade
in repository https://gitbox.apache.org/repos/asf/tvm.git
discard a5d1689846 update
omit 067286e2d2 Upgrade flashinfer 3rdparty module
add b1df4b0856 [Unity][Web][Fix] Fix fetchNDArray for f32-to-bf16 (#16294)
add faa8a0ad46 [Unity][nn.Module] Introduce operator `empty` (#16327)
add ac568eb30a [Unity] Fix PagedKVCache per FlashInfer update (#16317)
new d4d7f5d7e6 Upgrade flashinfer 3rdparty module
new 700a0215a1 update
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (a5d1689846)
\
N -- N -- N refs/heads/flashinfer-submodule-upgrade (700a0215a1)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
python/tvm/relax/frontend/nn/op.py | 59 +++++++++++++++++++++++++++++++
src/runtime/relax_vm/paged_kv_cache.cc | 10 +++---
tests/python/relax/test_frontend_nn_op.py | 27 ++++++++++++--
web/emcc/wasm_runtime.cc | 4 +--
web/src/runtime.ts | 2 +-
5 files changed, 90 insertions(+), 12 deletions(-)
