mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-26 07:26:09 +00:00

By allowing AnnotateAttr to be applied to statements, users can place arbitrary information in the AST for later use. For example, this can be used for HW-targeted language extensions that involve specialized loop annotations.
22 lines
1.3 KiB
C
22 lines
1.3 KiB
C
// RUN: %clang_cc1 %s -fsyntax-only -verify
|
|
|
|
void __attribute__((annotate("foo"))) foo(float *a) {
|
|
__attribute__((annotate("bar"))) int x;
|
|
[[clang::annotate("bar")]] int x2;
|
|
[[clang::annotate("bar")]] x2 += 1;
|
|
__attribute__((annotate(1))) int y; // expected-error {{expected string literal as argument of 'annotate' attribute}}
|
|
[[clang::annotate(1)]] int y2; // expected-error {{expected string literal as argument of 'annotate' attribute}}
|
|
__attribute__((annotate("bar", 1))) int z;
|
|
[[clang::annotate("bar", 1)]] int z2;
|
|
[[clang::annotate("bar", 1)]] z2 += 1;
|
|
|
|
int u = __builtin_annotation(z, (char*) 0); // expected-error {{second argument to __builtin_annotation must be a non-wide string constant}}
|
|
int v = __builtin_annotation(z, (char*) L"bar"); // expected-error {{second argument to __builtin_annotation must be a non-wide string constant}}
|
|
int w = __builtin_annotation(z, "foo");
|
|
float b = __builtin_annotation(*a, "foo"); // expected-error {{first argument to __builtin_annotation must be an integer}}
|
|
|
|
__attribute__((annotate())) int c; // expected-error {{'annotate' attribute takes at least 1 argument}}
|
|
[[clang::annotate()]] int c2; // expected-error {{'annotate' attribute takes at least 1 argument}}
|
|
[[clang::annotate()]] c2 += 1; // expected-error {{'annotate' attribute takes at least 1 argument}}
|
|
}
|