diff options
author | Douglas Gregor <dgregor@apple.com> | 2015-06-24 22:02:08 +0000 |
---|---|---|
committer | Douglas Gregor <dgregor@apple.com> | 2015-06-24 22:02:08 +0000 |
commit | aea7afdc1304cfef3b2cf61793729b1f55f26d0a (patch) | |
tree | 80670a6c9757e83d93e42c74128d0730cbaea889 /clang/test/FixIt/fixit-nullability-declspec.cpp | |
parent | 63d606bdcb606ace3cea3455dcaf0c3dac108d4e (diff) | |
download | bcm5719-llvm-aea7afdc1304cfef3b2cf61793729b1f55f26d0a.tar.gz bcm5719-llvm-aea7afdc1304cfef3b2cf61793729b1f55f26d0a.zip |
Replace __double_underscored type nullability qualifiers with _Uppercase_underscored
Addresses a conflict with glibc's __nonnull macro by renaming the type
nullability qualifiers as follows:
__nonnull -> _Nonnull
__nullable -> _Nullable
__null_unspecified -> _Null_unspecified
This is the major part of rdar://problem/21530726, but does not yet
provide the Darwin-specific behavior for the old names.
llvm-svn: 240596
Diffstat (limited to 'clang/test/FixIt/fixit-nullability-declspec.cpp')
-rw-r--r-- | clang/test/FixIt/fixit-nullability-declspec.cpp | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/clang/test/FixIt/fixit-nullability-declspec.cpp b/clang/test/FixIt/fixit-nullability-declspec.cpp index 2ac20b9d9b4..17989c3a885 100644 --- a/clang/test/FixIt/fixit-nullability-declspec.cpp +++ b/clang/test/FixIt/fixit-nullability-declspec.cpp @@ -4,6 +4,6 @@ // RUN: not %clang_cc1 -fixit -fblocks -Werror=nullability-declspec -x c++ %t // RUN: %clang_cc1 -fblocks -Werror=nullability-declspec -x c++ %t -__nullable int *ip1; // expected-error{{nullability specifier '__nullable' cannot be applied to non-pointer type 'int'; did you mean to apply the specifier to the pointer?}} -__nullable int (*fp1)(int); // expected-error{{nullability specifier '__nullable' cannot be applied to non-pointer type 'int'; did you mean to apply the specifier to the function pointer?}} -__nonnull int (^bp1)(int); // expected-error{{nullability specifier '__nonnull' cannot be applied to non-pointer type 'int'; did you mean to apply the specifier to the block pointer?}} +_Nullable int *ip1; // expected-error{{nullability specifier '_Nullable' cannot be applied to non-pointer type 'int'; did you mean to apply the specifier to the pointer?}} +_Nullable int (*fp1)(int); // expected-error{{nullability specifier '_Nullable' cannot be applied to non-pointer type 'int'; did you mean to apply the specifier to the function pointer?}} +_Nonnull int (^bp1)(int); // expected-error{{nullability specifier '_Nonnull' cannot be applied to non-pointer type 'int'; did you mean to apply the specifier to the block pointer?}} |