[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2020-11-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 Jonathan Wakely changed: What|Removed |Added Blocks||77691 --- Comment #10 from Jonathan

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-23 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 --- Comment #9 from Jonathan Wakely --- (In reply to Florian Weimer from comment #8) > The problem is that popular mallocs do not care about ABI and return > unaligned pointers for allocations smaller than the max_align_t alignment. > As a

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-23 Thread fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 Florian Weimer changed: What|Removed |Added CC||fw at gcc dot gnu.org --- Comment #8

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-23 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 --- Comment #7 from Jonathan Wakely --- The glibc change was https://sourceware.org/bugzilla/show_bug.cgi?id=21120 and is present from version 2.26

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 --- Comment #6 from Jonathan Wakely --- This bug also affects 32-bit GNU/Linux with older versions of glibc.

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 --- Comment #5 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #4) > Rainer, the change to gcc/cp/init.c would allow you to do: > > #define MALLOC_ABI_ALIGNMENT 8 Oops, it's in bits not bytes, so that should be #define

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 --- Comment #4 from Jonathan Wakely --- Rainer, the change to gcc/cp/init.c would allow you to do: #define MALLOC_ABI_ALIGNMENT 8 in gcc/config/i386/sol2.h and that would cause std::allocator to know that it can't rely on malloc for 16-byte

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-22 Thread jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 Jason Merrill changed: What|Removed |Added CC||jason at gcc dot gnu.org --- Comment #3

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/90569] __STDCPP_DEFAULT_NEW_ALIGNMENT__ is wrong for i386-pc-solaris2.11

2019-05-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90569 --- Comment #1 from Jonathan Wakely --- (I'm starting to think that __float128 support should have been disabled on targets where it requires greater alignment than malloc guarantees, instead of making GCC's max_align_t lie).