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/attributes.c

46 lines
1.6 KiB
C
Raw Normal View History

Fix a parser bug where we let attributes interfere with our disambiguation of whether a '(' was a grouping paren or the start of a function declarator. This is PR2796. Now we eat the attribute before deciding whether the paren is grouping or not, then apply it to the resultant decl or to the first argument as needed. One somewhat surprising aspect of this is that attributes interact with implicit int in cases like this: void a(x, y) // k&r style function void b(__attribute__(()) x, y); // function with two implicit int arguments void c(x, __attribute__(()) y); // error, can't have attr in identifier list. Fun stuff. llvm-svn: 57790
2008-10-20 10:05:46 +08:00
// RUN: clang -fsyntax-only -verify %s -pedantic -std=c99
new testcase llvm-svn: 39000
2006-10-17 11:00:45 +08:00
Fix a parser bug where we let attributes interfere with our disambiguation of whether a '(' was a grouping paren or the start of a function declarator. This is PR2796. Now we eat the attribute before deciding whether the paren is grouping or not, then apply it to the resultant decl or to the first argument as needed. One somewhat surprising aspect of this is that attributes interact with implicit int in cases like this: void a(x, y) // k&r style function void b(__attribute__(()) x, y); // function with two implicit int arguments void c(x, __attribute__(()) y); // error, can't have attr in identifier list. Fun stuff. llvm-svn: 57790
2008-10-20 10:05:46 +08:00
int __attribute__(()) x; // expected-warning {{extension used}}
// Hide __attribute__ behind a macro, to silence extension warnings about
// "__attribute__ being an extension".
#define attribute __attribute__
__inline void attribute((__always_inline__, __nodebug__))
foo(void) {
new testcase llvm-svn: 39000
2006-10-17 11:00:45 +08:00
}
Fix a parser bug where we let attributes interfere with our disambiguation of whether a '(' was a grouping paren or the start of a function declarator. This is PR2796. Now we eat the attribute before deciding whether the paren is grouping or not, then apply it to the resultant decl or to the first argument as needed. One somewhat surprising aspect of this is that attributes interact with implicit int in cases like this: void a(x, y) // k&r style function void b(__attribute__(()) x, y); // function with two implicit int arguments void c(x, __attribute__(()) y); // error, can't have attr in identifier list. Fun stuff. llvm-svn: 57790
2008-10-20 10:05:46 +08:00
attribute(()) y; // expected-warning {{defaults to 'int'}}
// PR2796
int (attribute(()) *z)(long y);
void f1(attribute(()) int x);
int f2(y, attribute(()) x); // expected-error {{expected identifier}}
// This is parsed as a normal argument list (with two args that are implicit
// int) because the attribute is a declspec.
void f3(attribute(()) x, // expected-warning {{defaults to 'int'}}
y); // expected-warning {{defaults to 'int'}}
void f4(attribute(())); // expected-error {{expected parameter declarator}}
// This is ok, the attribute applies to the pointer.
int baz(int (attribute(()) *x)(long y));
void g1(void (*f1)(attribute(()) int x));
void g2(int (*f2)(y, attribute(()) x)); // expected-error {{expected identifier}}
void g3(void (*f3)(attribute(()) x, int y)); // expected-warning {{defaults to 'int'}}
void g4(void (*f4)(attribute(()))); // expected-error {{expected parameter declarator}}
void (*h1)(void (*f1)(attribute(()) int x));
void (*h2)(int (*f2)(y, attribute(()) x)); // expected-error {{expected identifier}}
void (*h3)(void (*f3)(attribute(()) x)); // expected-warning {{defaults to 'int'}}
void (*h4)(void (*f4)(attribute(()))); // expected-error {{expected parameter declarator}}