https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71388
--- Comment #7 from David Abdurachmanov
---
Just for reference (if someone reads this PR):
https://gcc.gnu.org/ml/gcc/2016-02/msg00205.html
It contains a reference to C++ standard.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71388
--- Comment #6 from David Abdurachmanov
---
Agreed. As usual, thanks for verifying this. Will cook and send a patch to TBB.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71388
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71388
--- Comment #4 from Andreas Schwab ---
You should initialize the object in the constructor.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71388
--- Comment #3 from Andrew Pinski ---
Gcc considers the memset as being dead as nothing validly can assume anything
about the memory after the inplacement new.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71388
--- Comment #2 from David Abdurachmanov
---
Doesn't std::memset apply here? They allocate storage, set it to 0x0 and then
place construct the object.
At first look I wouldn't expect GCC to remove std::memset.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71388
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---