summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/utilsOsType.py
diff options
context:
space:
mode:
authorShoaib Meenai <smeenai@fb.com>2018-10-04 19:50:14 +0000
committerShoaib Meenai <smeenai@fb.com>2018-10-04 19:50:14 +0000
commitc8714d284a5aab04d829caeec54adcacb7a91cfc (patch)
tree7ffdf70ccb3f02e6a4d624c81046c938d3dc114d /lldb/scripts/utilsOsType.py
parent07dd5af6dfae6ff11d1c79dca892bf6277bd86c0 (diff)
downloadbcm5719-llvm-c8714d284a5aab04d829caeec54adcacb7a91cfc.tar.gz
bcm5719-llvm-c8714d284a5aab04d829caeec54adcacb7a91cfc.zip
[AST] Revert mangling changes from r339428
As discussed in https://reviews.llvm.org/D50144, we want Obj-C classes to have the same mangling as C++ structs, to support headers like the following: ``` @class I; struct I; void f(I *); ``` since the header can be used from both C++ and Obj-C++ TUs, and we want a consistent mangling across the two to prevent link errors. Itanium mangles both the same way, and so should the MS ABI. The main concern with having the same mangling for C++ structs and Obj-C classes was that we want to treat them differently for the purposes of exception handling, e.g. we don't want a C++ catch statement for a struct to be able to catch an Obj-C class with the same name as the struct. We can accomplish this by mangling Obj-C class names differently in their RTTI, which I'll do in a follow-up patch. Differential Revision: https://reviews.llvm.org/D52581 llvm-svn: 343808
Diffstat (limited to 'lldb/scripts/utilsOsType.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud