tmp/tmpfki3cykn/{from.md → to.md}
RENAMED
|
@@ -4,5 +4,20 @@ Except where otherwise specified, the provisions of
|
|
| 4 |
[[basic.stc.dynamic]] apply to the library versions of `operator new`
|
| 5 |
and `operator
|
| 6 |
delete`. If the value of an alignment argument passed to any of these
|
| 7 |
functions is not a valid alignment value, the behavior is undefined.
|
| 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 4 |
[[basic.stc.dynamic]] apply to the library versions of `operator new`
|
| 5 |
and `operator
|
| 6 |
delete`. If the value of an alignment argument passed to any of these
|
| 7 |
functions is not a valid alignment value, the behavior is undefined.
|
| 8 |
|
| 9 |
+
On freestanding implementations, it is *implementation-defined* whether
|
| 10 |
+
the default versions of the replaceable global allocation functions
|
| 11 |
+
satisfy the required behaviors described in [[new.delete.single]] and
|
| 12 |
+
[[new.delete.array]].
|
| 13 |
+
|
| 14 |
+
[*Note 1*: A freestanding implementation’s default versions of the
|
| 15 |
+
replaceable global allocation functions can cause undefined behavior
|
| 16 |
+
when invoked. During constant evaluation, the behaviors of those default
|
| 17 |
+
versions are irrelevant, as those calls are omitted
|
| 18 |
+
[[expr.new]]. — *end note*]
|
| 19 |
+
|
| 20 |
+
*Recommended practice:* If any of the default versions of the
|
| 21 |
+
replaceable global allocation functions meet the requirements of a
|
| 22 |
+
hosted implementation, they all should.
|
| 23 |
+
|