diff options
author | Akira Hatanaka <ahatanaka@apple.com> | 2017-06-27 04:34:04 +0000 |
---|---|---|
committer | Akira Hatanaka <ahatanaka@apple.com> | 2017-06-27 04:34:04 +0000 |
commit | 4b1c48441d8f094d5397a79482ba15dceb387b8c (patch) | |
tree | 995b6166bb83e531ea70247476217d36fe2f0eab /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h | |
parent | c9d9d7976a103e9551ff314323619890b54d4ab6 (diff) | |
download | bcm5719-llvm-4b1c48441d8f094d5397a79482ba15dceb387b8c.tar.gz bcm5719-llvm-4b1c48441d8f094d5397a79482ba15dceb387b8c.zip |
[CodeGen][ObjC] Fix GNU's encoding of bit-field ivars.
According to the documentation, when encoding a bit-field, GNU runtime
needs its starting position in addition to its type and size.
https://gcc.gnu.org/onlinedocs/gcc/Type-encoding.html
Prior to r297702, the starting position information was not being
encoded, which is incorrect, and after r297702, an assertion started to
fail because an ObjCIvarDecl was being passed to a function expecting a
FieldDecl.
This commit moves LookupFieldBitOffset to ASTContext and uses the
function to encode the starting position of bit-fields.
llvm-svn: 306364
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h')
0 files changed, 0 insertions, 0 deletions