summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python/edit-swig-python-wrapper-file.py
diff options
context:
space:
mode:
authorBill Wendling <isanbard@gmail.com>2011-09-30 23:19:55 +0000
committerBill Wendling <isanbard@gmail.com>2011-09-30 23:19:55 +0000
commit9925f197cce894e8913d38e9b259935219a69fc6 (patch)
tree7a6499f7882c137a1f96b84ba9dab86906c68600 /lldb/scripts/Python/edit-swig-python-wrapper-file.py
parentf56c0137e2593cd580c7cb4bbc9d7adb13ea5c98 (diff)
downloadbcm5719-llvm-9925f197cce894e8913d38e9b259935219a69fc6.tar.gz
bcm5719-llvm-9925f197cce894e8913d38e9b259935219a69fc6.zip
When inferring the pointer alignment, if the global doesn't have an initializer
and the alignment is 0 (i.e., it's defined globally in one file and declared in another file) it could get an alignment which is larger than the ABI allows for that type, resulting in aligned moves being used for unaligned loads. For instance, in file A.c: struct S s; In file B.c: struct { // something long }; extern S s; void foo() { struct S p = s; // ... } this copy is a 'memcpy' which is turned into a series of 'movaps' instructions on X86. But this is wrong, because 'struct S' has alignment of 4, not 16. llvm-svn: 140902
Diffstat (limited to 'lldb/scripts/Python/edit-swig-python-wrapper-file.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud