public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114940] std::generator relies on an optional overload of operator delete Date: Tue, 28 May 2024 09:20:08 +0000 [thread overview] Message-ID: <bug-114940-4-2xWrC20rlk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114940-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114940 --- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-14 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:89dff1488ef3fde11f6451e5f9817e14bcd6a873 commit r14-10250-g89dff1488ef3fde11f6451e5f9817e14bcd6a873 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed May 22 10:32:43 2024 +0100 libstdc++: Guard use of sized deallocation [PR114940] Clang does not enable -fsized-deallocation by default, which means it can't compile our <stacktrace> and <generator> headers. Make the __cpp_lib_generator macro depend on the compiler-defined __cpp_sized_deallocation macro, and change <stacktrace> to use unsized deallocation when __cpp_sized_deallocation isn't defined. libstdc++-v3/ChangeLog: PR libstdc++/114940 * include/bits/version.def (generator): Depend on __cpp_sized_deallocation. * include/bits/version.h: Regenerate. * include/std/stacktrace (_GLIBCXX_SIZED_DELETE): New macro. (basic_stacktrace::_Impl::_M_deallocate): Use it. (cherry picked from commit b2fdd508d7e63158e9d2a6dd04f901d02900def3)
next prev parent reply other threads:[~2024-05-28 9:20 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-03 19:39 [Bug libstdc++/114940] New: " liuxf19 at 163 dot com 2024-05-03 19:56 ` [Bug libstdc++/114940] " liuxf19 at 163 dot com 2024-05-03 19:57 ` redi at gcc dot gnu.org 2024-05-03 19:57 ` redi at gcc dot gnu.org 2024-05-03 20:08 ` liuxf19 at 163 dot com 2024-05-04 8:47 ` arsen at gcc dot gnu.org 2024-05-04 11:02 ` redi at gcc dot gnu.org 2024-05-04 12:10 ` arsen at gcc dot gnu.org 2024-05-22 9:30 ` redi at gcc dot gnu.org 2024-05-22 9:37 ` redi at gcc dot gnu.org 2024-05-22 22:30 ` cvs-commit at gcc dot gnu.org 2024-05-28 9:20 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-28 11:08 ` cvs-commit at gcc dot gnu.org 2024-05-28 11:09 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114940-4-2xWrC20rlk@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).