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++/94295] use __builtin_operator_new and __builtin_operator_delete when available
Date: Thu, 22 Jul 2021 13:43:17 +0000 [thread overview]
Message-ID: <bug-94295-4-0j52sDz4Uu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94295-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94295
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:c9ca352186226ae757688e160e7c6f394c9f26aa
commit r12-2470-gc9ca352186226ae757688e160e7c6f394c9f26aa
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Jul 22 14:38:34 2021 +0100
libstdc++: Use __builtin_operator_new when available [PR94295]
Clang provides __builtin_operator_new and __builtin_operator_delete,
which have the same semantics as ::operator new and ::operator delete
except that the compiler is allowed to elide calls to them. This changes
std::allocator to use those built-in functions so that memory allocated
by std::allocator can be optimized away when using Clang. This avoids an
abstraction penalty for using std::allocator to allocate storage rather
than a new-expression.
Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
libstdc++-v3/ChangeLog:
PR libstdc++/94295
* include/ext/new_allocator.h (_GLIBCXX_OPERATOR_NEW)
(_GLIBCXX_OPERATOR_DELETE, _GLIBCXX_SIZED_DEALLOC): Define.
(allocator::allocate, allocator::deallocate): Use new macros.
next prev parent reply other threads:[~2021-07-22 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 23:16 [Bug libstdc++/94295] New: " richard-gccbugzilla at metafoo dot co.uk
2020-03-24 7:04 ` [Bug libstdc++/94295] " glisse at gcc dot gnu.org
2020-03-24 20:26 ` richard-gccbugzilla at metafoo dot co.uk
2020-03-24 20:44 ` pinskia at gcc dot gnu.org
2020-03-24 21:04 ` richard-gccbugzilla at metafoo dot co.uk
2020-03-24 21:34 ` glisse at gcc dot gnu.org
2020-03-24 21:58 ` richard-gccbugzilla at metafoo dot co.uk
2020-03-26 20:08 ` glisse at gcc dot gnu.org
2021-07-19 16:06 ` redi at gcc dot gnu.org
2021-07-20 18:58 ` richard-gccbugzilla at metafoo dot co.uk
2021-07-20 19:00 ` redi at gcc dot gnu.org
2021-07-20 19:31 ` jason at gcc dot gnu.org
2021-07-20 19:44 ` redi at gcc dot gnu.org
2021-07-22 13:43 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-22 13:44 ` 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-94295-4-0j52sDz4Uu@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).