llvm-project/clang
Gabor Marton 0b57ccb7b5 [ASTImporter] Refactor unittests to be able to parameterize them in a more flexible way
Summary:
Currently `TestImportBase` is derived from `ParameterizedTestsFixture`
which explicitly states that the gtest parameter can be only an
`ArgVector`. This is a limitation when we want to create tests which may
have different parameters.
E.g. we would like to create tests where we can combine different test
parameters. So, for example we'd like gtest to be able to provide
parameters of `<std::tuple<ArgVector, const char *>` instead of a simple
`ArgVector`.

Reviewers: a_sidorin, shafik, a.sidorin

Subscribers: rnkovacs, dkrupp, Szelethus, gamesh411, cfe-commits

Differential Revision: https://reviews.llvm.org/D57322

llvm-svn: 353425
2019-02-07 16:52:48 +00:00
..
INPUTS
bindings Fix python3 compability issue in clang binding 2019-01-24 10:34:44 +00:00
cmake Move the SMT API to LLVM 2019-02-07 03:19:45 +00:00
docs [DOCS]Support for emission of the debug info for the Cuda devices, NFC. 2019-02-05 20:38:36 +00:00
examples Update the file headers across all of the LLVM projects in the monorepo 2019-01-19 08:50:56 +00:00
include Typo: s/follwing/following 2019-02-07 11:13:28 +00:00
lib Fix r350643 to limit COFF emission to <= 32 BYTES instead of BITS. 2019-02-07 15:14:11 +00:00
runtime [CMake] External compiler-rt-configure requires LLVMTestingSupport when including tests 2019-02-01 15:35:25 +00:00
test Fix r350643 to limit COFF emission to <= 32 BYTES instead of BITS. 2019-02-07 15:14:11 +00:00
tools [OpenMP 5.0] Parsing/sema support for "omp declare mapper" directive. 2019-02-01 20:25:04 +00:00
unittests [ASTImporter] Refactor unittests to be able to parameterize them in a more flexible way 2019-02-07 16:52:48 +00:00
utils [analyzer] [testing] Inside CmpRuns.py output also print the filename of the first item in the path 2019-02-05 22:26:57 +00:00
www [analyzer] Document RetainCountChecker behavior and annotations 2019-02-05 22:27:10 +00:00
.arcconfig
.clang-format
.clang-tidy Disable tidy checks with too many hits 2019-02-01 11:20:13 +00:00
.gitignore Adjust documentation for git migration. 2019-01-29 16:37:27 +00:00
CMakeLists.txt Move the SMT API to LLVM 2019-02-07 03:19:45 +00:00
CODE_OWNERS.TXT Add myself as code owner for OpenBSD driver 2018-11-30 21:42:34 +00:00
INSTALL.txt
LICENSE.TXT Fix typos throughout the license files that somehow I and my reviewers 2019-01-21 09:52:34 +00:00
ModuleInfo.txt
NOTES.txt PTH-- Remove feature entirely- 2018-12-04 14:34:09 +00:00
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/