en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/lang/objc/bitfield_ivars/Makefile#d1a1798e [lldb] Replace unneeded use of Foundation with ObjectiveC in tests (NFC)When referencing `NSObject`, it's enough to import `objc/NSObject.h`. Importing `Foundation` is unnecessary in these cases.Differential Revision: https://reviews.llvm.org/D99867 List of files: /llvm-project-15.0.7/lldb/test/API/lang/objc/bitfield_ivars/Makefile Sun, 04 Apr 2021 21:52:26 +0000 Dave Lee <davelee.com@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/lang/objc/bitfield_ivars/Makefile#a54c42df Fix how we handle bit-fields for Objective-C when creating an ASTCurrently expressions dealing with bit-fields in Objective-C objects is pretty broken. When generating debug-info for Objective-C bit-fields DW_AT_data_bit_offset has a different meaning than it does to C and C++.When we parse the DWARF we validate bit offsets for C and C++ correctly but not for ObjC. For ObjC in some cases we end up incorrectly flagging an error and we don't generate further bit-fields in the AST.Later on when we do a name lookup we don't find the ObjCIvarDecl in the ObjCInterfaceDecl in some cases since we never added it and then we don't go to the runtime to obtain the offset.This will fix how we handle bit-fields for the Objective-C case and add tests to verify this fix but also to documents areas that still don't work and will be addressed in follow-up PRs.Note: we can never correctly calculate offsets statically because of how Objective-C deals with the fragile base class issue. Which means the runtime may need to shift fields over.Differential Revision: https://reviews.llvm.org/D83433 List of files: /llvm-project-15.0.7/lldb/test/API/lang/objc/bitfield_ivars/Makefile Mon, 20 Jul 2020 23:09:18 +0000 shafik <syaghmour@apple.com>