clang-tests/gcc-4_2-testsuite/src/gcc.dg/cpp/ucnid-4.c

/* { dg-do compile } */
/* { dg-options "-std=c99" } */

int \u00AA;
int \u00AB; /* { dg-error "expected identifier" } */
int \u00B6; /* { dg-error "expected identifier" } */
int \u00BA;
int \u00C0;
int \u00D6;

/* APPLE LOCAL <rdar://problem/13134700> */
/* GCC doesn't warn about this character in gnu99 mode because it's valid in
   C++03. If we do implement a similar extension, though, we'll just use the
   full set of valid C11 characters. */
int \u0384; /* { dg-error "expected identifier" } */

int \u0669; /* { dg-error "expected identifier" } */
int A\u0669;

/* APPLE LOCAL <rdar://problem/13134700> */
/* These are valid preprocessor numeric tokens, but invalid parsing tokens.
   Clang will accept the former, but there's no way to tell if it's made up
   of one token or two. */
#define TOKEN1 0\u00BA; 
#define TOKEN2 0\u0669;

int \u0E59; /* { dg-error "expected identifier" } */
int A\u0E59;