forked from OSchip/llvm-project
5be71faf4b
Summary: The current install-clang-headers target installs clang's resource directory headers. This is different from the install-llvm-headers target, which installs LLVM's API headers. We want to introduce the corresponding target to clang, and the natural name for that new target would be install-clang-headers. Rename the existing target to install-clang-resource-headers to free up the install-clang-headers name for the new target, following the discussion on cfe-dev [1]. I didn't find any bots on zorg referencing install-clang-headers. I'll send out another PSA to cfe-dev to accompany this rename. [1] http://lists.llvm.org/pipermail/cfe-dev/2019-February/061365.html Reviewers: beanz, phosek, tstellar, rnk, dim, serge-sans-paille Subscribers: mgorny, javed.absar, jdoerfert, #sanitizers, openmp-commits, lldb-commits, cfe-commits, llvm-commits Tags: #clang, #sanitizers, #lldb, #openmp, #llvm Differential Revision: https://reviews.llvm.org/D58791 llvm-svn: 355340 |
||
---|---|---|
.. | ||
CMakeLists.txt | ||
README.txt | ||
Test.cxx | ||
main.cpp |
README.txt
This is an example of Clang based interpreter, for executing standalone C/C++ programs. It demonstrates the following features: 1. Parsing standard compiler command line arguments using the Driver library. 2. Constructing a Clang compiler instance, using the appropriate arguments derived in step #1. 3. Invoking the Clang compiler to lex, parse, syntax check, and then generate LLVM code. 4. Use the LLVM JIT functionality to execute the final module. 5. Intercepting a Win64 library call to allow throwing and catching exceptions in and from the JIT. The implementation has many limitations and is not designed to be a full fledged interpreter. It is designed to demonstrate a simple but functional use of the Clang compiler libraries.