summaryrefslogtreecommitdiffstats
path: root/clang/test/Analysis
diff options
context:
space:
mode:
authorAnders Carlsson <andersca@mac.com>2010-09-03 00:25:02 +0000
committerAnders Carlsson <andersca@mac.com>2010-09-03 00:25:02 +0000
commitaf7534f08496c118a8575a7adbbd5715a624e4a0 (patch)
tree6cb4ea7e5f39f15947a09107758f105dcd626af2 /clang/test/Analysis
parent09c8fbe812d9dfde2c6b665ecf5d1f4e87d16c69 (diff)
downloadbcm5719-llvm-af7534f08496c118a8575a7adbbd5715a624e4a0.tar.gz
bcm5719-llvm-af7534f08496c118a8575a7adbbd5715a624e4a0.zip
Get rid of the "functions declared 'noreturn' should have a 'void' result type" warning.
The rationale behind this is that it is normal for callback functions to have a non-void return type and it should still be possible to mark them noreturn. (JavaScriptCore is a good example of this). llvm-svn: 112918
Diffstat (limited to 'clang/test/Analysis')
-rw-r--r--clang/test/Analysis/misc-ps.m2
1 files changed, 1 insertions, 1 deletions
diff --git a/clang/test/Analysis/misc-ps.m b/clang/test/Analysis/misc-ps.m
index 6727e7da3bb..4fbaa49c116 100644
--- a/clang/test/Analysis/misc-ps.m
+++ b/clang/test/Analysis/misc-ps.m
@@ -323,7 +323,7 @@ int test_invalidate_by_ref() {
// was the block containing the merge for '?', which would trigger an
// assertion failure.
int rdar_7027684_aux();
-int rdar_7027684_aux_2() __attribute__((noreturn)); // expected-warning{{functions declared 'noreturn' should have a 'void' result type}}
+int rdar_7027684_aux_2() __attribute__((noreturn));
void rdar_7027684(int x, int y) {
{}; // this empty compound statement is critical.
(rdar_7027684_aux() ? rdar_7027684_aux_2() : (void) 0);
OpenPOWER on IntegriCloud