Hi!
The nullability-00.m* tests unfortunately check the exact spelling of
the diagnostics I've changed earlier today.
Tested on x86_64-linux and i686-linux, committed to trunk as obvious.
2024-04-23 Jakub Jelinek <ja...@redhat.com>
* objc.dg/attributes/nullability-00.m: Adjust expected diagnostic
spelling: recognised -> recognized.
* obj-c++.dg/attributes/nullability-00.mm: Likewise.
--- gcc/testsuite/objc.dg/attributes/nullability-00.m.jj 2020-11-13
13:50:23.365551538 +0100
+++ gcc/testsuite/objc.dg/attributes/nullability-00.m 2024-04-23
17:37:18.978721522 +0200
@@ -8,7 +8,7 @@ __attribute__((objc_nullability("unspeci
__attribute__((objc_nullability("nullable"))) id c;
__attribute__((objc_nullability("nonnull"))) id d;
__attribute__((objc_nullability("resettable"))) id e;
-__attribute__((objc_nullability("nonsense"))) id e_3; /* { dg-error
{'objc_nullability' attribute argument '"nonsense"' is not recognised} } */
+__attribute__((objc_nullability("nonsense"))) id e_3; /* { dg-error
{'objc_nullability' attribute argument '"nonsense"' is not recognized} } */
__attribute__((objc_nullability(noGoingToWork))) id e_4; /* { dg-error
{'noGoingToWork' undeclared here} } */
@interface MyRoot
--- gcc/testsuite/obj-c++.dg/attributes/nullability-00.mm.jj 2020-11-13
13:50:23.361551584 +0100
+++ gcc/testsuite/obj-c++.dg/attributes/nullability-00.mm 2024-04-23
17:37:35.717500341 +0200
@@ -8,7 +8,7 @@ __attribute__((objc_nullability("unspeci
__attribute__((objc_nullability("nullable"))) id c;
__attribute__((objc_nullability("nonnull"))) id d;
__attribute__((objc_nullability("resettable"))) id e;
-__attribute__((objc_nullability("nonsense"))) id e_3; /* { dg-error
{'objc_nullability' attribute argument '"nonsense"' is not recognised} } */
+__attribute__((objc_nullability("nonsense"))) id e_3; /* { dg-error
{'objc_nullability' attribute argument '"nonsense"' is not recognized} } */
__attribute__((objc_nullability(noGoingToWork))) id e_4; /* { dg-error
{'noGoingToWork' was not declared in this scope} } */
@interface MyRoot
Jakub
