Date: Fri, 27 Oct 2023 00:59:34 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 274706] The C++ header 'execution' is missing Message-ID: <bug-274706-99-RQkBhmRXr5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274706-99@https.bugs.freebsd.org/bugzilla/> References: <bug-274706-99@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274706 --- Comment #3 from Mark Millard <marklmi26-fbsd@yahoo.com> --- More from the stndard places for libc++ status information, in this case: https://libcxx.llvm.org/UsingLibcxx.html reports (probably for llvm17 or so at this point): QUOTE . . . Those are disabled by default because they are neither API nor ABI stable. However, the -fexperimental-library compiler flag can be defined to turn those features on. The following features are currently considered experimental and are only provided when -fexperimental-library is passed: The parallel algorithms library (<execution> and the associated algorithms) std::stop_token, std::stop_source and std::stop_callback std::jthread std::chrono::tzdb and related time zone functionality std::ranges::join_view END QUOTE This need to use -fexperimental-library to enable features has been mentioned in various prior submittals of supposedly missing features in FreeBSD's LLVM (but are really things that still have an API or ABI that is not yet known stable in libc++: not yet known to be well implemented). At this point I do not know if FreeBSD has -fexperimental-library working for use of <execution> or not for stable/13 . I may see about setting up an experiment based on a snapshot image at some point. I'm also not sure of the LLVM 16 status vs. LLVM17+ status upstream. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274706-99-RQkBhmRXr5>