llvm-project/clang/test/Lexer/utf-16.c

// RUN: %clang_cc1 %s -fsyntax-only -verify
// rdar://7876588

// This test verifies that clang gives a decent error for UTF-16 source files.

#include "utf-16.c.txt" // expected-error {{UTF-16 (LE) byte order mark detected}}
Fix tests that weren't actually verifying anything. Passing -verify to clang without -cc1 or -Xclang silently passes (with a printed warning, but lit doesn't care about that). This change adds -cc1 or, as is necessary in one case, -Xclang to fix this so that these tests are actually verifying as intended. I'd like to change the driver so this kind of mistake could not be made, but I'm not entirely sure how. Further, since the driver only warns about unknown flags in general, we could have similar bugs with a misspellings of arguments that would be nice to find. llvm-svn: 154776 2012-04-16 06:09:44 +08:00			`// RUN: %clang_cc1 %s -fsyntax-only -verify`
enhance sourcemgr to detect various UTF BOM's and emit a fatal error about it instead of producing tons of garbage from the lexer. It would be even better for sourcemgr to dynamically transcode (e.g. from UTF16 -> UTF8). llvm-svn: 101924 2010-04-21 02:14:03 +08:00			`// rdar://7876588`

push some source location information down through the compiler, into ContentCache::getBuffer. This allows it to produce diagnostics on the broken #include line instead of without a location. llvm-svn: 101939 2010-04-21 04:35:58 +08:00			`// This test verifies that clang gives a decent error for UTF-16 source files.`

			`#include "utf-16.c.txt" // expected-error {{UTF-16 (LE) byte order mark detected}}`