Date: Sun, 02 Oct 2022 17:59:23 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 266748] '#include <memory_resource>' isn't available despite it being required by c++17 Message-ID: <bug-266748-99-p4UfZUEBDn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266748-99@https.bugs.freebsd.org/bugzilla/> References: <bug-266748-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=3D266748 --- Comment #4 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Yuri Victorovich from comment #3) The various: https://en.cppreference.com/w/cpp/compiler_support/* are good thing to look at when the default environment seems to have insufficient features. The pages also cover "GCC libstdc++" in addition to "Clang libc++", as well as core language features for GCC and for Clang. For officially released vintages of the C++ standard, GCC and GCC libstdc++ tend to have more complete coverage in some version than LLVM clang++ and its libc++ does. For either LLVM or GCC, the vintage may at times need to be newer than the FreeBSD ports available or the system-clang++ version in FreeBSD's main [so: in 14 currently]. libc++ does not have port-specific versions, however. The LLVM ports use the system's libc++ . This can also lead to GCC libstdc++ having better language coverage for more modern C++ vintages. --=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-266748-99-p4UfZUEBDn>