]> granicus.if.org Git - clang/commit
projects / clang / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 917edde) | patch
Add speculative clang-interpreter test
authorAlp Toker <alp@nuanti.com>
Mon, 5 May 2014 06:22:21 +0000 (06:22 +0000)
committerAlp Toker <alp@nuanti.com>
Mon, 5 May 2014 06:22:21 +0000 (06:22 +0000)
commit230adb86e945fbf5be5a362ee14c7534ebe19567
tree93fa5ee4f9edc9d491ae6e1e53b07c199393eadbtree | snapshot
parent917eddeac502213fc3d19eae90e2c8ae5820311ecommit | diff
Add speculative clang-interpreter test

Let's see how far this gets on the build servers. The application requires
native JIT and uses the C standard library, but hopefully we can get this
tested on at least some configurations.

Taking a lead from the clang-format tests, we'll just expect the executable to
get picked up from the build output path for now.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@207950 91177308-0d34-0410-b5e6-96231b3b80d8
test/Misc/interpreter.c [new file with mode: 0644] blob
Unnamed repository; edit this file 'description' to name the repository.