Skip to content

chore: build kernels against torch 2.14.0 - #24

Open
faresobeid wants to merge 2 commits into
mainfrom
chore/torch-2.14
Open

faresobeid wants to merge 2 commits into
mainfrom
chore/torch-2.14

Conversation

@faresobeid

Copy link
Copy Markdown
Contributor

vLLM 0.33.0 pins torch 2.14.0 (PrimeIntellect-ai/prime-rl#4365). prime-kernels, deep-ep, deep-gemm and deep-select are torch C++ extensions bound to the libtorch ABI: the current prime_kernels-0.1.0+cu130torch2.13.0 wheel fails to import on torch 2.14 (undefined symbol in flash_moe/_C).

One-line change: TORCH_VERSION: 2.13.0+cu130 -> 2.14.0+cu130. The version stamp step then produces +cu130torch2.14.0. CUDA tag and builder images are unchanged. torchao only uses the stable ABI (aoti_torch_*), so its rebuild is a no-op for compatibility.

Not included: DeepGEMM 2.5.0 -> 2.8.1 (vLLM 0.33 vendors vllm-project/DeepGEMM@0820030); that stays in #20, together with prime-rl's fp8_mqa_logits -> fp8_fp4_mqa_logits change.

🤖 Generated with Claude Code

faresobeid and others added 2 commits November 2, 2026 19:48
vLLM 0.33.0 pins torch 2.14.0. prime-kernels, deep-ep, deep-gemm and
deep-select are torch C++ extensions bound to the torch ABI, so prime-rl
needs them rebuilt (PrimeIntellect-ai/prime-rl#4365).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
faresobeid added a commit to PrimeIntellect-ai/prime-rl that referenced this pull request Nov 2, 2026
…orch 2.14

From PrimeIntellect-ai/prime-kernels release v0.1.0-b050074 (PrimeIntellect-ai/prime-kernels#24).
torchao stays on v0.1.1: it only uses the stable libtorch ABI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant