llvm-project/clang
Nico Weber 9084adc290 clang-cl: Support MSVC2015's /validate-charset flag.
Clang always assumes that files are utf-8. If an invalidly encoded character is
used in an identifier, clang always errors. If it's used in a character
literal, clang warns Winvalid-source-encoding (on by default). Clang never
checks the encoding of things in comments (adding this seems like a nice
feature if it doesn't impact performance).

For cl.exe /utf-8 (which enables /validate-charset), if a bad character is used
in an identifier, it emits both an error and a warning. If it's used in a
literal or a comment, it emits a warning.

So mapping /validate-charset to -Winvalid-source-encoding seems like a fairly
decent fit.

https://reviews.llvm.org/D23945

llvm-svn: 279872
2016-08-26 21:51:14 +00:00
..
INPUTS
bindings bindings: expose diagnostic formatting to Python 2016-08-11 05:31:07 +00:00
cmake [CMake] Adding toolchain targets to PGO and Apple CMake caches 2016-08-17 21:51:38 +00:00
docs Fixed a typo (compilation_commands.json --> compile_commands.json). 2016-08-19 13:36:31 +00:00
examples Reapply r276973 "Adjust Registry interface to not require plugins to export a registry" 2016-08-05 11:01:08 +00:00
include clang-cl: Support MSVC2015's /validate-charset flag. 2016-08-26 21:51:14 +00:00
lib clang-cl: Accept MSVC 2015's `/execution-charset:utf-8` flag. 2016-08-26 21:11:43 +00:00
runtime [CMake] Adding USES_TERMINAL to a few additional custom targets 2016-06-28 20:30:52 +00:00
test clang-cl: Support MSVC2015's /validate-charset flag. 2016-08-26 21:51:14 +00:00
tools Fix memory leaks in clang-offload-bundler 2016-08-25 07:21:34 +00:00
unittests clang-format: [JS] nested and tagged template strings. 2016-08-25 10:13:21 +00:00
utils [Order Files] On Darwin use DTrace's oneshot probe 2016-08-24 22:09:46 +00:00
www [www] Add nullability questions to analyzer FAQ. 2016-08-19 22:04:45 +00:00
.arcconfig Upgrade all the .arcconfigs to https. 2016-07-14 13:15:37 +00:00
.clang-format
.clang-tidy Try to use readability-identifier-naming check on Clang. 2016-04-13 08:59:49 +00:00
.gitignore Add the clang debug info test directory to .gitignore as it's managed separately. 2016-01-29 01:35:55 +00:00
CMakeLists.txt driver: Support checking for rlimits via cmake (when bootstrapping) 2016-08-23 20:07:07 +00:00
CODE_OWNERS.TXT Added Anastasia Stulova as a code owner for OpenCL 2016-02-03 18:51:19 +00:00
INSTALL.txt
LICENSE.TXT Update copyright year to 2016. 2016-03-30 22:38:44 +00:00
ModuleInfo.txt
NOTES.txt
README.txt

README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source-level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:              http://clang.llvm.org/
Building and using Clang:          http://clang.llvm.org/get_started.html
Clang Static Analyzer:             http://clang-analyzer.llvm.org/
Information on the LLVM project:   http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/