Date: Wed, 05 Apr 2023 16:54:55 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 255374] C++20 features (headers) std::concepts, std::format, std::numbers, std::source_location, etc. are missing Message-ID: <bug-255374-99-STQK5hlppb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255374-99@https.bugs.freebsd.org/bugzilla/> References: <bug-255374-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=3D255374 --- Comment #22 from Mark Millard <marklmi26-fbsd@yahoo.com> --- Turns out that opensuse tumblweed can install llvm16 related materials such that -stdlib=3Dlibc++ can be used. Based on this it appears that for the llvm16 __cpp_lib_... feature test macros vs. the existing main Freebsd ones: If fully adopted, the libc++ would go from having undefined status to having the modern values for: __cpp_lib_constexpr_complex __cpp_lib_constexpr_vector __cpp_lib_memory_resource __cpp_lib_polymorphic_allocator __cpp_lib_source_location Also, __cpp_lib_ranges would go from undefined to 202106 . C++20 also has a later 202110 . C++23 has 3 later values, the last being 202211 . (I'm generally omitting the L suffixes in my materials.) It does not appear that any other __cpp_lib_... macros would change values. These notes are based on using -std=3Dc++20 . Other notes: __cpp_lib_int_pow2 in my prior note turned out to be from it not being in the sort order position for the join operation in the material that I copied/genrated and processed. It is in fact up to date in main FreeBSD. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255374-99-STQK5hlppb>