History log of /external/llvm/utils/llvm-lit/llvm-lit.in
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
c6a4f5e819217e1e12c458aed8e7b122e23a3a58 21-Jul-2014 Stephen Hines <srhines@google.com> Update LLVM for rebase to r212749.

Includes a cherry-pick of:
r212948 - fixes a small issue with atomic calls

Change-Id: Ib97bd980b59f18142a69506400911a6009d9df18
/external/llvm/utils/llvm-lit/llvm-lit.in
36b56886974eae4f9c5ebc96befd3e7bfe5de338 24-Apr-2014 Stephen Hines <srhines@google.com> Update to LLVM 3.5a.

Change-Id: Ifadecab779f128e62e430c2b4f6ddd84953ed617
/external/llvm/utils/llvm-lit/llvm-lit.in
1917aaff29566f4c2fc9cd857e00bdededdff7ce 27-Jan-2013 NAKAMURA Takumi <geek4civic@gmail.com> [CMake][Lit][unittests] Deprecate CMAKE_BUILD_TYPE in each build directory for unittests.

For example,
cur) unittests/ADT/Release/ADTTests
new) unittests/ADT/ADTTests

RUNTIME_BUILD_MODE can be substituted to CMAKE_CFG_INTDIR.

With Make and Ninja, the tree is not built with multiple configurations.
Then, including the build type in target directory doesn't make sense.
See also "How can I build multiple modes without switching?"
http://www.cmake.org/Wiki/CMake_FAQ
CMAKE_CFG_INTDIR is set to "."

With multiple-configuration-aware build system, like Visual Studio, each unittest is built on appropriate directory, for example,
unittests/ADT/Release/ADTTests.exe
CMAKE_CFG_INTDIR is set to build system's variable, like "$(Configuration)" or "$(OutDir)".

Thus, "--param build_config" is also deprecated.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@173616 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/utils/llvm-lit/llvm-lit.in
7a9572f8af035a7c9e6a6be236a285c9eef55488 05-Sep-2012 David Blaikie <dblaikie@gmail.com> [LIT] Add a clang_tools_extra_site_cfg to match the various other site_cfg.

This doesn't seem ideal, perhaps we could just keep the llvm_site_cfg and have
other config (clang and clang-tools-extra) derive their site_cfg from that.

Suggestions/complaints/ideas welcome.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@163171 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/utils/llvm-lit/llvm-lit.in
90275ea2ee7c7a960a3567926140b26a526b0aa1 19-Apr-2012 Daniel Dunbar <daniel@zuster.org> llvm-lit: Inject the lit module path at the beginning of sys.path, just in case
the user has another lit somewhere.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@155131 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/utils/llvm-lit/llvm-lit.in
4203b7116a807d0c4dabcb403664f0cca0a7f9f7 09-Feb-2011 NAKAMURA Takumi <geek4civic@gmail.com> llvm-lit may be available with CMake.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@125168 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/utils/llvm-lit/llvm-lit.in
ce83025ad1bb8984d68cfd004c93b7f5d19e69e9 09-Feb-2011 NAKAMURA Takumi <geek4civic@gmail.com> llvm-lit may be able to invoke clang tests.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@125167 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/utils/llvm-lit/llvm-lit.in
b7698a49c2a9e732fa02c7ebee98ca5c7173b5fc 02-Aug-2010 Daniel Dunbar <daniel@zuster.org> tests: Add an 'llvm-lit' tool (script), which gets generated as part of the
build and has the object build directory baked into it. This allows 'llvm-lit'
to properly find the information needed to run the test suite in all cases,
without requiring the user to have LLVM or 'lit' available in their PATH, for
example.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@110000 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/utils/llvm-lit/llvm-lit.in