Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Vulkan][32-bit] non-dispatchable handles do not fit in void* on i586

未关闭
#3,182 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
cpp
领域
backend

调研方向

从 src/vt/vulkan/vulkan_context.cpp 开始,跟踪 VkBuffer 和 VkDeviceMemory 的静态断言,然后检查 Pack/Unpack 路径,以及存储这些句柄的公共后端上下文字段。使用 -DVLLM_CPP_VULKAN=ON 在 i586 上构建 v0.0.2;完成标准是 Vulkan 后端能够编译,且不会通过 void* 传递不可分发的句柄。

由索引模型根据 Issue 内容生成。

描述

Problem

The Vulkan backend does not compile on 32-bit x86/i586. In src/vt/vulkan/vulkan_context.cpp, it asserts that Vulkan handles fit in void*:

static_assert(sizeof(VkBuffer) <= sizeof(void*), "VkBuffer must fit in void*");
static_assert(sizeof(VkDeviceMemory) <= sizeof(void*), "VkDeviceMemory must fit in void*");

With the Vulkan headers on i586, the assertions fail because the comparison is 8 <= 4. Vulkan non-dispatchable handles such as VkBuffer and VkDeviceMemory are 64-bit values even when the host pointer size is 32-bit.

The backend then packs these handles through void* in Pack/Unpack, and the public backend context stores buffer and memory handles as void*, so simply removing the assertions would not be sufficient.

Reproducer

Build v0.0.2 on i586 with:

-DVLLM_CPP_VULKAN=ON

The build fails in src/vt/vulkan/vulkan_context.cpp with:

error: static assertion failed: VkBuffer must fit in void*
the comparison reduces to (8 <= 4)
error: static assertion failed: VkDeviceMemory must fit in void*
the comparison reduces to (8 <= 4)

Proposed direction

Use an architecture-independent opaque handle representation, such as a dedicated 64-bit storage type for non-dispatchable handles, and avoid packing them into void*. Dispatchable pointer handles can remain pointer-sized.

The openSUSE package currently disables the Vulkan backend on 32-bit x86 as a downstream workaround.

主要语言
C++
星标
440
派生
55
平均合并
1 天 4 小时
30 天内合并 PR
346

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

mudler/vllm.cpp 的其他 Issue

查看 mudler/vllm.cpp 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。