main doesn't compile with nvcc 13.0 (Linux, GCC 12/13 host): __connect_declfn_v, __transform_completion_signatures, __receiver_adaptor
維護者通常 2 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 一週以上
- 新手友好度
- 18/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- cpp
- 領域
- build-system
研究方向
The failures come from headers in include/stdexec/__detail: __connect.hpp around lines 77-110, __receiver_adaptor.hpp line 125, __transform_completion_signatures.hpp lines 360 and 400, and __typeinfo.hpp line 101. Reproduce by compiling the nvcc_basic.cu snippet with nvcc 13.0 and the flags in the issue. Done means that snippet compiles and the new CI job passes, which needs maintainer agreement on supporting nvcc first.
由索引模型根據 Issue 內容生成。
描述
At current main (1d58877ad898fa3422658d47b28f67deb9c10e80), nvcc can't compile a basic sender chain in a .cu file. Tested in nvidia/cuda:13.0.0-devel-ubuntu24.04 with nvcc V13.0.48 and GCC 13.3 (default) or GCC 12.4 (-ccbin g++-12) as host compiler; both give the same errors. Related: #2402 (nvcc with an MSVC host, which has additional problems).
// nvcc_basic.cu
#include <stdexec/execution.hpp>
int main()
{
auto s = stdexec::just(41) | stdexec::then([](int i) { return i + 1; });
auto [v] = stdexec::sync_wait(std::move(s)).value();
return v == 42 ? 0 : 1;
}
nvcc -std=c++20 --extended-lambda --expt-relaxed-constexpr -arch=sm_89 -I stdexec/include nvcc_basic.cu
Errors (paths shortened, repeated lines removed):
include/stdexec/__detail/__connect.hpp(83): error: declaration is incompatible with variable template "stdexec::__connect::__connect_declfn_v" (declared at line 77)
include/stdexec/__detail/__connect.hpp(90): error: declaration is incompatible with variable template "stdexec::__connect::__connect_declfn_v" (declared at line 77)
include/stdexec/__detail/__connect.hpp(103): error: declaration is incompatible with variable template "stdexec::__connect::__connect_declfn_v" (declared at line 97)
include/stdexec/__detail/__connect.hpp(110): error: declaration is incompatible with variable template "stdexec::__connect::__connect_declfn_v" (declared at line 97)
include/stdexec/__detail/__receiver_adaptor.hpp(125): error: expected a ">"
include/stdexec/__detail/__receiver_adaptor.hpp(125): error: too few arguments for concept template "std::derived_from"
include/stdexec/__detail/__receiver_adaptor.hpp(125): error: qualified name is not allowed
include/stdexec/__detail/__typeinfo.hpp(101): error: static assertion failed
include/stdexec/__detail/__transform_completion_signatures.hpp(360): error: type name is not allowed
include/stdexec/__detail/__transform_completion_signatures.hpp(400): error: type name is not allowed
include/stdexec/__detail/__sync_wait.hpp(353): error: no instance of function template "stdexec::connect_t::operator()" matches the argument list
include/stdexec/__detail/__sync_wait.hpp(355): error: static assertion failed with "..."
As far as I can see, the CI doesn't build anything with nvcc: the GPU jobs use clang and nvc++, the CPU jobs don't compile CUDA. That would explain why this goes unnoticed.
HPX compiles stdexec in .cu files and has been carrying patches for nvcc (https://github.com/TheHPXProject/hpx/tree/master/cmake, HPX_StdexecNvcc*.patch). Against 04de75de58, the revision HPX uses today, the patched stdexec compiles this program with nvcc 13.0. The largest patch (HPX_StdexecNvccWorkarounds.patch, which changes __connect.hpp, __receiver_adaptor.hpp, __transform_completion_signatures.hpp, __typeinfo.hpp, __env.hpp and __counting_scopes.hpp) no longer applies to main, and with the three HPX patches that still apply (AsyncScopeNvcc, which is #2304, CudaStdAtomic and NvccDiagnostics) main still fails with the errors above.
Is nvcc meant to be supported? If yes, would you take a CI job with nvcc (for example nvcc 13 with GCC 13 as host compiler, compiling the tests as CUDA sources) and PRs that bring HPX's workarounds to main? We'd be happy to help with those.
- 主要語言
- C++
- 星號
- 2.5k
- 分支
- 285
- 平均合併
- 2 天 5 小時
- 30 天內合併 PR
- 82
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
NVIDIA/stdexec 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 2 天內回覆
-
難度 4/5 3-5 天 新手友好度 18/100
維護者通常 2 天內回覆
-
難度 3/5 1-3 小時 新手友好度 25/100
維護者通常 2 天內回覆
-
難度 5/5 一週以上 新手友好度 12/100
維護者通常 2 天內回覆
-
難度 1/5 1 小時以內 新手友好度 15/100
NVIDIA/stdexec#2342 · 2 則留言 · 3 個 reaction ·
維護者通常 2 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 80/100
-
難度 1/5 1 小時以內 新手友好度 82/100
-
難度 2/5 1-3 小時 新手友好度 72/100
eclipse-score/lifecycle#929 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
colbymchenry/codegraph#3223 ·
維護者通常 1 天內回覆