Closed
Bug 1560666
Opened 5 years ago
Closed 5 years ago
turn off support for C++17 aligned new/delete overloads
Categories
(Core :: Memory Allocator, enhancement)
Core
Memory Allocator
Tracking
()
RESOLVED
FIXED
mozilla70
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: froydnj, Assigned: froydnj)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
See the "since C++17" variants in https://en.cppreference.com/w/cpp/memory/new/operator_new
...and for that matter, https://en.cppreference.com/w/cpp/memory/new/operator_delete
Assignee | ||
Comment 1•5 years ago
|
||
Turning off support for them is easier than writing the code for them.
Summary: handle new C++17 operator new/delete overloads → turn off support for C++17 aligned new/delete overloads
Assignee | ||
Comment 2•5 years ago
|
||
Just like C++14 sized deallocation support, we don't want to support
this. We shouldn't be using new
on over-aligned types anyway.
Pushed by nfroyd@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f4aa9fbabdcb
turn off C++17 aligned allocation support; r=glandium
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
Updated•5 years ago
|
Assignee: nobody → nfroyd
You need to log in
before you can comment on or make changes to this bug.
Description
•