File: n3505.c

package info (click to toggle)
llvm-toolchain-21 1%3A21.1.6-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,245,028 kB
  • sloc: cpp: 7,619,726; ansic: 1,434,018; asm: 1,058,748; python: 252,740; f90: 94,671; objc: 70,685; lisp: 42,813; pascal: 18,401; sh: 8,601; ml: 5,111; perl: 4,720; makefile: 3,675; awk: 3,523; javascript: 2,409; xml: 892; fortran: 770
file content (32 lines) | stat: -rw-r--r-- 1,153 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
// RUN: %clang_cc1 -verify -std=c2y -Wall -pedantic %s
// RUN: %clang_cc1 -verify -std=c23 -Wall -pedantic %s
// RUN: %clang_cc1 -verify -std=c11 -Wall -pedantic %s
// RUN: %clang_cc1 -verify -std=c99 -Wall -pedantic %s

/* WG14 N3505: Yes
 * Preprocessor integer expressions, v. 2
 *
 * This introduces a constraint that preprocessing tokens must be an integer
 * literal, character literal, punctuator, or some other implementation-defined
 * sequence of tokens (to support builtins that insert odd tokens into the
 * parsing stream).
 */

// This is technically an integer constant expression, but it does not match
// the new constraints and thus needs to be diagnosed.
#if 1 ? 1 : (""[0] += 5) // expected-error {{invalid token at start of a preprocessor expression}}
#endif

// But with a character literal, it is fine.
#if 1 ? 1 : ('a' + 5) // Ok
#endif

// This doesn't mean that all punctuators are fine, however.
#if 1 ? 1 : ('a' += 5) // expected-error {{token is not a valid binary operator in a preprocessor subexpression}}
#endif

// But some are.
#if 1 ? 1 : ~('a') // Ok
#endif

int x; // Needs a declaration to avoid a pedantic warning