Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/build_kernels.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ env:
# — see Dockerfile.cuda in prime-rl), deliberately different from `build`'s (see the
# portability comment up top and the per-arch images in the `build` matrix below).
CONTAINER_IMAGE: nvidia/cuda:13.0.3-devel-ubuntu24.04
TORCH_VERSION: 2.13.0+cu130
TORCH_VERSION: 2.14.0+cu130

jobs:
build:
Expand Down
4 changes: 4 additions & 0 deletions scripts/install_deep_gemm.sh
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,10 @@ git clone --recurse-submodules "$DEEPGEMM_GIT_REPO" "$TMPDIR/DeepGEMM"
cd "$TMPDIR/DeepGEMM"
git checkout "$DEEPGEMM_GIT_REF"
git submodule update --init --recursive
# torch >= 2.14 headers require C++20 (ATen.h errors out below it); this DeepGEMM rev still
# builds its extension as C++17. vLLM's DeepGEMM fork made the same switch.
sed -i "s/'-std=c++17'/'-std=c++20'/" setup.py
grep -q "'-std=c++20'" setup.py || { echo "ERROR: could not switch DeepGEMM to C++20" >&2; exit 1; }

# Back to the invocation directory: a relative --wheel-dir must resolve there, not
# inside $TMPDIR, which the EXIT trap deletes before the caller ever sees the wheel.
Expand Down
Loading