diff options
| author | Martin Storsjo <martin@martin.st> | 2018-02-27 06:27:06 +0000 |
|---|---|---|
| committer | Martin Storsjo <martin@martin.st> | 2018-02-27 06:27:06 +0000 |
| commit | 96b01bcfb685a2156488712e6c634303e2c8c41b (patch) | |
| tree | cd91d4339fa5d6e60d19f9dd63a893959c2429a6 /lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py | |
| parent | 41ffd96445e19401004e41f583a5efe338986a08 (diff) | |
| download | bcm5719-llvm-96b01bcfb685a2156488712e6c634303e2c8c41b.tar.gz bcm5719-llvm-96b01bcfb685a2156488712e6c634303e2c8c41b.zip | |
[RecordLayout] Don't align to non-power-of-2 sizes when using -mms-bitfields
When targeting GNU/MinGW for i386, the size of the "long double" data
type is 12 bytes (while it is 8 bytes in MSVC). When building
with -mms-bitfields to have struct layouts match MSVC, data types
are laid out in a struct with alignment according to their size.
However, this doesn't make sense for the long double type, since
it doesn't match MSVC at all, and aligning to a non-power-of-2
size triggers other asserts later.
This matches what GCC does, aligning a long double to 4 bytes
in structs on i386 even when -mms-bitfields is specified.
This fixes asserts when using the max_align_t data type when
building for MinGW/i386 with the -mms-bitfields flag.
Differential Revision: https://reviews.llvm.org/D43734
llvm-svn: 326173
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py')
0 files changed, 0 insertions, 0 deletions
