From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Add sized-deallocation functions to discussion of new/delete
Date: Thu, 30 May 2019 15:03:00 -0000 [thread overview]
Message-ID: <20190530150334.GN2599@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 19 bytes --]
Committed to CVS.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1286 bytes --]
Index: htdocs/gcc-9/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-9/porting_to.html,v
retrieving revision 1.5
diff -u -r1.5 porting_to.html
--- htdocs/gcc-9/porting_to.html 13 May 2019 11:57:03 -0000 1.5
+++ htdocs/gcc-9/porting_to.html 30 May 2019 15:01:55 -0000
@@ -144,15 +144,17 @@
<p>
The simplest solution is to only replace the ordinary
<code>operator new(size_t)</code> and
-<code>operator delete(void*)</code>
+<code>operator delete(void*)</code> and
+<code>operator delete(void*, size_t)</code>
functions, and the replaced versions will be used by all of
<code>operator new(size_t, nothrow_t)</code>,
<code>operator new[](size_t)</code> and
<code>operator new[](size_t, nothrow_t)</code>
and the corresponding <code>operator delete</code> functions.
To support types with extended alignment you may also need to replace
-<code>operator new(size_t, std::align_val_t)</code> and
-<code>operator delete(void*, std::align_val_t)</code>
+<code>operator new(size_t, align_val_t)</code> and
+<code>operator delete(void*, align_val_t)</code> and
+<code>operator delete(void*, align_val_t)</code>
(which will then be used by the <code>nothrow</code> and array forms for
extended alignments).
</p>
reply other threads:[~2019-05-30 15:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190530150334.GN2599@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@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).