diff options
author | Akira Hatanaka <ahatanaka@apple.com> | 2018-03-28 21:13:14 +0000 |
---|---|---|
committer | Akira Hatanaka <ahatanaka@apple.com> | 2018-03-28 21:13:14 +0000 |
commit | fcbe17c6be86c87031822c1c01d8b43b6d142695 (patch) | |
tree | 701edbfeeae78c64ed7133dead94509fd4abcc04 /clang/lib/Basic/FileSystemStatCache.cpp | |
parent | aac23d78814d45039c0a8b3dbf204d5664df854c (diff) | |
download | llvm-fcbe17c6be86c87031822c1c01d8b43b6d142695.zip llvm-fcbe17c6be86c87031822c1c01d8b43b6d142695.tar.gz llvm-fcbe17c6be86c87031822c1c01d8b43b6d142695.tar.bz2 |
[ObjC++] Make parameter passing and function return compatible with ObjC
ObjC and ObjC++ pass non-trivial structs in a way that is incompatible
with each other. For example:
typedef struct {
id f0;
__weak id f1;
} S;
// this code is compiled in c++.
extern "C" {
void foo(S s);
}
void caller() {
// the caller passes the parameter indirectly and destructs it.
foo(S());
}
// this function is compiled in c.
// 'a' is passed directly and is destructed in the callee.
void foo(S a) {
}
This patch fixes the incompatibility by passing and returning structs
with __strong or weak fields using the C ABI in C++ mode. __strong and
__weak fields in a struct do not cause the struct to be destructed in
the caller and __strong fields do not cause the struct to be passed
indirectly.
Also, this patch fixes the microsoft ABI bug mentioned here:
https://reviews.llvm.org/D41039?id=128767#inline-364710
rdar://problem/38887866
Differential Revision: https://reviews.llvm.org/D44908
llvm-svn: 328731
Diffstat (limited to 'clang/lib/Basic/FileSystemStatCache.cpp')
0 files changed, 0 insertions, 0 deletions