#1570 Vulkan 永远不会被拆除: 没有引擎调用 coli_vk_shutdown (Metal 是如此,在 kimi_k3 中)

coli vk shutdown ()' 被宣布(c/后端 vulkan.h:20')并定义 (c/backend vulkan.c1536'),但树上唯一的呼叫站点在树上 ifdef VK TEST'自我测试main ()' (c/backend vulkan.c:2163')。没有引擎呼叫内容:

|:也.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ============= ================================================================================================================================================================================================================================================= `qwen36.c' | 0 | 0 | +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

因此,Metal ** 被拆下,在kimi k3.c' (:3214',3269',3342'),而Vulkan 从来没有任何地方。

对于一个CLI,退出这是无害的—— 过程撕裂还原设备, 竞技场块和地图上的记忆。这似乎值得问因为 `mat release'本身的评论提出了具体情况,涉及:

{\fn黑体\fs22\bord1\shad0\3aHBE\4aH00\fscx67\fscy66\2cHFFFFFF\3cH808080}没有自由的领带

motori nello stesso 处理不, e motore che 非 si smonta diventa una 富人平均寿命。

今天没有一个树上引擎在一个过程中,所以这很可能是故意的——因此是一个问题而不是一补一补。

** 不对称是故意的吗? ** 如果引擎会把Vulkan拆掉,看起来就像交叉变化(每个引擎都有一个Vulkan路径,而不是一个),我会如果你愿意的话很乐意把它作为单独的公关寄出去

央视"主"@"a8f2ca6",v1.11.0.

用[Claude代码]起草(https://Claude.com/Claude代码)