- User Since
- Jan 23 2017, 3:27 PM (155 w, 4 d)
Sep 25 2019
Note that MS-STL already has this behavior, while libstdc++ does not.
Aug 15 2019
FWIW I think this particular bug was https://gcc.gnu.org/PR65942
Jun 25 2019
Apr 24 2019
I added a patch to https://bugs.llvm.org/show_bug.cgi?id=41578 that fixes it differently.
Feb 13 2019
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89345#c3 for what I've done in libstdc++
As it looks like libc++ isn't going to define the type for earlier dialects, libstdc++ doesn't either (which seems right anyway because the names aren't reserved prior to C++20).
Feb 7 2019
Jan 23 2019
Jan 17 2019
I'd be happy to restrict this to > C++17 only (which is automatically the case when using G++ because there's no -fdestroying-delete to enable it, you only get it with -std=c++2a, -std=gnu++2a etc.)
Jan 16 2019
The simplest solution would be to change libstdc++'s <new> to:
May 9 2018
@chandlerc thanks for catching this.
Jan 23 2017
The __throw_xxx functions are not part of the public libstdc++ API and whatever Firefox is trying to do with them is not supported by libstdc++ and is undefined behaviour. Make it stop.