Repository navigation
0.20.0: a SYCL build has one C++ runtime, libstdc++ - #51
Open
Sunrisepeak wants to merge 2 commits into
Open
Sunrisepeak wants to merge 2 commits into
Sunrisepeak wants to merge 2 commits into
Conversation
libsycl.so throws sycl::exception on libstdc++, and a typed catch does not match across two C++ runtimes in one process (mcpp-community/mcpp#838). The rule put -l:libstdc++.so.6 beside the libc++ an llvm build links; it now names no C++ library, refuses a build whose C++ library is not libstdc++ with both remedies (gcc.libstdcxx beside llvm, or a gcc toolchain), and points --gcc-install-dir at the build's own GCC: the graph's supplier (MCPP_CXX_ABI_ROOT), the gcc toolchain's payload, or the xim:gcc it declares. The SYCL consumer takes gcc.libstdcxx and the runtime adapter under the accelerator, so the CPU variant keeps libc++. Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
The consumers, the editor lane and the bootstrap run mcpp 2026.10.26.1, which the SYCL consumer's llvm build over gcc.libstdcxx needs. Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
0.20.0: a SYCL build has one C++ runtime, and it is libstdc++ (mcpp-community/mcpp#841, mcpp#838).
libsycl.sothrowssycl::exceptionon libstdc++. A typed catch does not match across two C++ runtimes in one process, so 0.19's-l:libstdc++.so.6beside an llvm build's libc++ let onlycatch (...)see what the runtime threw. Changes:mcpp.rules.syclnames no C++ library on the link line. On Linux it refuses a build whose C++ library (mcpp::cxx_stdlib()) is not libstdc++, before any unit is compiled, and names both remedies (gcc.libstdcxxbeside llvm, or a gcc toolchain).--gcc-install-dirfollows the build's own GCC, in this order: the graph's supplier (MCPP_CXX_ABI_ROOT, read from the environment so the rule still compiles on older engines), the gcc toolchain's payload, then thexim:gccthe rule declares.tests/sycl-consumerdeclaresgcc.libstdcxxand the runtime adapter undercfg(accelerator = "sycl"), so the CPU variant (--no-accel) keeps llvm's libc++.docs/rules.md), version 0.20.0. CI runs mcpp 2026.10.26.1.Measured locally with dpcpp 7.1.0:
gcc.libstdcxx: builds and runs.--no-accel: builds and runs on libc++.The SYCL consumer needs
gcc.libstdcxxfrom mcpplibs/mcpp-index#568.Co-authored-by: speak-agent 248744407+speak-agent@users.noreply.github.com