maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Parser/stmt-attributes.m

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

58 lines
1.8 KiB
Mathematica
Raw Normal View History

[Attr] Apply GNU-style attributes to expression statements Before this commit, expression statements could not be annotated with statement attributes. Whenever parser found attribute, it unconditionally assumed that it was followed by a declaration. This not only doesn't allow expression attributes to have attributes, but also produces spurious error diagnostics. In order to maintain all previously compiled code, we still assume that GNU attributes are followed by declarations unless ALL of those are statement attributes. And even in this case we are not forcing the parser to think that it should parse a statement, but rather let it proceed as if no attributes were found. Differential Revision: https://reviews.llvm.org/D93630
2020-12-21 17:05:14 +08:00
// RUN: %clang_cc1 -verify %s \
// RUN: -fblocks -fobjc-exceptions -fexceptions -fsyntax-only \
// RUN: -Wno-unused-value -Wno-unused-getter-return-value
#if !__has_extension(statement_attributes_with_gnu_syntax)
#error "We should have statement attributes with GNU syntax support"
#endif
@interface Base
@end
@interface Test : Base
@property(getter=hasFoobar) int foobar;
- (void)foo;
- (void)bar;
@end
Use functions with prototypes when appropriate; NFC A significant number of our tests in C accidentally use functions without prototypes. This patch converts the function signatures to have a prototype for the situations where the test is not specific to K&R C declarations. e.g., void func(); becomes void func(void); This is the fifth batch of tests being updated (there are a significant number of other tests left to be updated). Note, the behavior of -ast-print is broken. It prints functions with a prototype (void) as if they have no prototype () in C. Some tests need to disable strict prototype checking when recompiling the results of an -ast-print invocation.
2022-02-09 22:10:10 +08:00
Test *getTest(void);
[Attr] Apply GNU-style attributes to expression statements Before this commit, expression statements could not be annotated with statement attributes. Whenever parser found attribute, it unconditionally assumed that it was followed by a declaration. This not only doesn't allow expression attributes to have attributes, but also produces spurious error diagnostics. In order to maintain all previously compiled code, we still assume that GNU attributes are followed by declarations unless ALL of those are statement attributes. And even in this case we are not forcing the parser to think that it should parse a statement, but rather let it proceed as if no attributes were found. Differential Revision: https://reviews.llvm.org/D93630
2020-12-21 17:05:14 +08:00
@implementation Test
- (void)foo __attribute__((nomerge)) {
// expected-error@-1 {{'nomerge' attribute only applies to functions and statements}}
}
- (void)bar {
__attribute__(()) [self foo];
// expected-error@-1 {{missing '[' at start of message send expression}}
// expected-error@-2 {{expected ']'}}
// expected-error@-3 {{expected identifier or '('}}
// expected-note@-4 {{to match this '['}}
__attribute__((nomerge)) [self foo];
[clang] inheritance fix for nomerge attribute Discussed here: https://reviews.llvm.org/D119061#3310822 Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119451
2022-02-11 22:49:06 +08:00
// expected-warning@-1 {{'nomerge' attribute is ignored because there exists no call expression inside the statement}}
[Attr] Apply GNU-style attributes to expression statements Before this commit, expression statements could not be annotated with statement attributes. Whenever parser found attribute, it unconditionally assumed that it was followed by a declaration. This not only doesn't allow expression attributes to have attributes, but also produces spurious error diagnostics. In order to maintain all previously compiled code, we still assume that GNU attributes are followed by declarations unless ALL of those are statement attributes. And even in this case we are not forcing the parser to think that it should parse a statement, but rather let it proceed as if no attributes were found. Differential Revision: https://reviews.llvm.org/D93630
2020-12-21 17:05:14 +08:00
__attribute__((nomerge)) [getTest() foo];
__attribute__(()) ^{};
// expected-error@-1 {{expected identifier or '('}}
__attribute__((nomerge)) ^{};
[clang] inheritance fix for nomerge attribute Discussed here: https://reviews.llvm.org/D119061#3310822 Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119451
2022-02-11 22:49:06 +08:00
// expected-warning@-1 {{'nomerge' attribute is ignored because there exists no call expression inside the statement}}
[Attr] Apply GNU-style attributes to expression statements Before this commit, expression statements could not be annotated with statement attributes. Whenever parser found attribute, it unconditionally assumed that it was followed by a declaration. This not only doesn't allow expression attributes to have attributes, but also produces spurious error diagnostics. In order to maintain all previously compiled code, we still assume that GNU attributes are followed by declarations unless ALL of those are statement attributes. And even in this case we are not forcing the parser to think that it should parse a statement, but rather let it proceed as if no attributes were found. Differential Revision: https://reviews.llvm.org/D93630
2020-12-21 17:05:14 +08:00
__attribute__((nomerge)) ^{ [self foo]; }();
__attribute__(()) @try {
[self foo];
} @finally {
}
__attribute__((nomerge)) @try {
[getTest() foo];
} @finally {
}
__attribute__((nomerge)) (__bridge void *)self;
[clang] inheritance fix for nomerge attribute Discussed here: https://reviews.llvm.org/D119061#3310822 Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119451
2022-02-11 22:49:06 +08:00
// expected-warning@-1 {{'nomerge' attribute is ignored because there exists no call expression inside the statement}}
[Attr] Apply GNU-style attributes to expression statements Before this commit, expression statements could not be annotated with statement attributes. Whenever parser found attribute, it unconditionally assumed that it was followed by a declaration. This not only doesn't allow expression attributes to have attributes, but also produces spurious error diagnostics. In order to maintain all previously compiled code, we still assume that GNU attributes are followed by declarations unless ALL of those are statement attributes. And even in this case we are not forcing the parser to think that it should parse a statement, but rather let it proceed as if no attributes were found. Differential Revision: https://reviews.llvm.org/D93630
2020-12-21 17:05:14 +08:00
__attribute__((nomerge)) self.hasFoobar;
[clang] inheritance fix for nomerge attribute Discussed here: https://reviews.llvm.org/D119061#3310822 Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119451
2022-02-11 22:49:06 +08:00
// expected-warning@-1 {{'nomerge' attribute is ignored because there exists no call expression inside the statement}}
[Attr] Apply GNU-style attributes to expression statements Before this commit, expression statements could not be annotated with statement attributes. Whenever parser found attribute, it unconditionally assumed that it was followed by a declaration. This not only doesn't allow expression attributes to have attributes, but also produces spurious error diagnostics. In order to maintain all previously compiled code, we still assume that GNU attributes are followed by declarations unless ALL of those are statement attributes. And even in this case we are not forcing the parser to think that it should parse a statement, but rather let it proceed as if no attributes were found. Differential Revision: https://reviews.llvm.org/D93630
2020-12-21 17:05:14 +08:00
}
@end