C++20 coroutine frame layout mismatch when linking object files from different compilers
The C++20 standard defines coroutine semantics and the promise_type concept but leaves coroutine frame layout, handle representation, and intrinsic calling conventions as implementation-defined. GCC, Clang, and MSVC each emit distinct frame structures and symbol mangling for coroutine state machines, so translation units built with different toolchains canno
cpp