[Bug middle-end/94992] gcc thinks a member variable is uninitialised

2020-05-08 Thread rafael at espindo dot la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94992 --- Comment #3 from Rafael Avila de Espindola --- For completeness, this is a reduction of a std::swap(x,x). The placement new was originally in the move assignment operator. I was able to reproduce this with gcc 9 by moving a few functions out

[Bug middle-end/94992] gcc thinks a member variable is uninitialised

2020-05-07 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94992 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug middle-end/94992] gcc thinks a member variable is uninitialised

2020-05-07 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94992 --- Comment #1 from Andrew Pinski --- Comment on attachment 48477 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48477 testcase >my_future f2; >new (&f2) my_future(std::move(f2)); This is going to be problematic as f2 is being cre