[Bug c++/82021] Unnecessary null pointer check in global placement new (and also in any class-specific placement new operator declared as noexcept)

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82021

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Jonathan Wakely  ---
See PR 35878, the commit was r246301

*** This bug has been marked as a duplicate of bug 35878 ***

[Bug c++/82021] Unnecessary null pointer check in global placement new (and also in any class-specific placement new operator declared as noexcept)

[glisse at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82021

--- Comment #3 from Marc Glisse  ---
You can search for "Ville Voutilainen", the patch was this year, not long
before the release so maybe March.

[Bug c++/82021] Unnecessary null pointer check in global placement new (and also in any class-specific placement new operator declared as noexcept)

[carl.cook at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82021

--- Comment #2 from Carl Cook  ---
Thanks Marc, that was it. I'd tried with no std=X flags, and std=c+=11. 

Definitely a DUP. I didn't find any related bug reports when skimming through
bugzilla, but that's probably just my fault.

Incidentally, if you have a sha of the commit(s) that fixed this, please let me
know, I'd be interested in taking a look.

[Bug c++/82021] Unnecessary null pointer check in global placement new (and also in any class-specific placement new operator declared as noexcept)

[glisse at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82021

--- Comment #1 from Marc Glisse  ---
Did you try with -std=c++1z? (if that solves your issue, this is a DUP, it
should be enabled in all mode, but it isn't yet)