Strict aliasing warning with Android GCC 4.9 about concurrentqueue HOT 6 CLOSED

Hmm, that's unfortunate. In that case, is it even possible (in a standard-compliant way) to declare an object with enough bytes for N T objects without initializing said memory?

from concurrentqueue.

Ooh. Apparently C++11 allows non-POD types in unions now, for exactly this kind of scenario. The constructors/destructor are not called automatically, which is exactly what I was trying to avoid with my char[] workaround. I'll try that if MSVC supports it.

from concurrentqueue.

Aw, no, unions can't hold any type with a non-trivial copy constructor.
It looks like there's no built-in way to do this sort of manual memory management. However, I can use intermediate casts to hopefully trick the compiler into doing the right thing. See http://stackoverflow.com/questions/13466556/aligned-storage-and-strict-aliasing

from concurrentqueue.

Let me know if this fixes the warning. Thanks!

from concurrentqueue.

Seems fine.

from concurrentqueue.

Great, thank you!

from concurrentqueue.