mirror of
https://github.com/RPCS3/llvm.git
synced 2025-05-18 03:16:13 +00:00
caeade4234
Summary: This patch is provided in preparation for removing autoconf on 1/26. The proposal to remove autoconf on 1/26 was discussed on the llvm-dev thread here: http://lists.llvm.org/pipermail/llvm-dev/2016-January/093875.html "I felt a great disturbance in the [build system], as if millions of [makefiles] suddenly cried out in terror and were suddenly silenced. I fear something [amazing] has happened." - Obi Wan Kenobi Reviewers: chandlerc, grosbach, bob.wilson, tstellarAMD, echristo, whitequark Subscribers: chfast, simoncook, emaste, jholewinski, tberghammer, jfb, danalbert, srhines, arsenm, dschuff, jyknight, dsanders, joker.eph, llvm-commits Differential Revision: http://reviews.llvm.org/D16471 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@258861 91177308-0d34-0410-b5e6-96231b3b80d8
//===----------------------------------------------------------------------===/ // Kaleidoscope with MCJIT //===----------------------------------------------------------------------===// The files in this directory are meant to accompany the first in a series of three blog posts that describe the process of porting the Kaleidoscope tutorial to use the MCJIT execution engine instead of the older JIT engine. When the blog post is ready this file will be updated with a link to the post. The source code in this directory combines all previous versions, including the old JIT-based implementation, into a single file for easy comparison with command line options to select between the various possibilities. This directory contain a Makefile that allow the code to be built in a standalone manner, independent of the larger LLVM build infrastructure. To build the program you will need to have 'clang++' and 'llvm-config' in your path. If you attempt to build using the LLVM 3.3 release, some minor modifications will be required. This directory also contains a Python script that may be used to generate random input for the program and test scripts to capture data for rough performance comparisons. Another Python script will split generated input files into definitions and function calls for the purpose of testing the IR input and caching facilities.