This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/70441] vector<__float128> crashes on two push_back calls with -mavx
- From: "glisse at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 29 Mar 2016 20:17:08 +0000
- Subject: [Bug c++/70441] vector<__float128> crashes on two push_back calls with -mavx
- Auto-submitted: auto-generated
- References: <bug-70441-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70441
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
C++ does not support dynamic allocation of over-aligned types (usually SIMD
vectors, but also __float128 on x86 for instance). C++17 will partially support
it (operator new), but still not fix the std::vector case, which has to wait
until C++20 (assuming someone actually does the work of writing and pushing a
proposal) :-(
Well, actually, you can always write your own allocator which provides properly
aligned memory.