[Bug c++/70066] alignas imposes the wrong limit on data members

2016-03-03 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70066 Martin Sebor changed: What|Removed |Added Blocks||58601 --- Comment #5 from Martin Sebor -

[Bug c++/70066] alignas imposes the wrong limit on data members

2016-03-03 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70066 Andrew Pinski changed: What|Removed |Added Target||x86_64-*-* --- Comment #4 from Andrew Pi

[Bug c++/70066] alignas imposes the wrong limit on data members

2016-03-03 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70066 --- Comment #3 from Andrew Pinski --- This is the definition which matters: /* Minimum size in bits of the largest boundary to which any and all fundamental data types supported by the hardware might need to be aligned. No data type wants

[Bug c++/70066] alignas imposes the wrong limit on data members

2016-03-03 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70066 --- Comment #2 from Andrew Pinski --- > The BIGGEST_FIELD_ALIGNMENT macro is defined in config/i386/i386.h with the > following comment: ... > #ifdef IN_TARGET_LIBS This definition version is only ever used in libobjc and libgcc.

[Bug c++/70066] alignas imposes the wrong limit on data members

2016-03-03 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70066 Martin Sebor changed: What|Removed |Added Known to fail||4.9.3, 5.3.0, 6.0 --- Comment #1 from Mar