public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108391] '::operator delete(void*, size_t)' was not found when clang compiled libstdc++
Date: Fri, 13 Jan 2023 13:25:49 +0000 [thread overview]
Message-ID: <bug-108391-4-csEkNyrKAU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108391-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108391
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to jinci kang from comment #3)
> So what do you think I should do?
> ```cpp
> #ifdef __clang__
> #define __cpp_sized_deallocation
> #endif
No, don't do that! That has undefined behaviour.
> I think this is a bit troublesome, this API can be used directly after C++14.
Well like I said, it's a clang bug. The C++ standard requires the macro to be
defined, but if Clang doesn't do that, the library won't declare the
corresponding API.
You should report this to Clang, not here.
next prev parent reply other threads:[~2023-01-13 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 9:43 [Bug libstdc++/108391] New: Operator '::operator delete(void*, size_t)' was not found when clang compiled stdlibc++ jincikang at gmail dot com
2023-01-13 12:54 ` [Bug libstdc++/108391] '::operator delete(void*, size_t)' was not found when clang compiled libstdc++ redi at gcc dot gnu.org
2023-01-13 13:00 ` redi at gcc dot gnu.org
2023-01-13 13:08 ` jincikang at gmail dot com
2023-01-13 13:14 ` jakub at gcc dot gnu.org
2023-01-13 13:17 ` jincikang at gmail dot com
2023-01-13 13:25 ` redi at gcc dot gnu.org [this message]
2023-01-13 13:40 ` jakub at gcc dot gnu.org
2023-01-13 13:46 ` jincikang at gmail dot com
2023-01-13 13:50 ` jincikang at gmail dot com
2023-01-13 13:53 ` redi at gcc dot gnu.org
2023-01-13 13:54 ` jincikang at gmail dot com
2023-01-13 14:20 ` redi at gcc dot gnu.org
2023-01-13 15:52 ` jincikang at gmail dot com
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-108391-4-csEkNyrKAU@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: link
Be 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).