Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I can’t comment on mavieth’s answer, but I think their conclusion is correct; the libstdc++ std module doesn’t use the oneTBB backend. It seems like the problem is that oneTBB, when included as he...
#1: Initial revision
by
Indi
·
2026-08-14T20:16:51Z (about 1 month ago)
I can’t comment on [mavieth’s answer](https://software.codidact.com/posts/296542/296544#answer-296544), but I think their conclusion is correct; the libstdc++ `std` module doesn’t use the oneTBB backend. It seems like the problem is that [oneTBB, when included as headers, injects translation-unit-local stuff into the module purview… which is not allowed](https://www.mail-archive.com/[email protected]/msg412363.html). [oneTBB *is* modularized (`import tbb;`, see the third line in the table)](https://arewemodulesyet.org/projects/), so if you wanted to use it in a modules context, you could… but you’d have to use the actual oneTBB API, not the standard API. We will probably have to wait for libstdc++ and oneTBB to sort out their issues before libstdc++ can use oneTBB as a back-end during a modules build.