Mehdi Amini c94da20917 Make DataLayout Non-Optional in the Module
Summary:
DataLayout keeps the string used for its creation.

As a side effect it is no longer needed in the Module.
This is "almost" NFC, the string is no longer
canonicalized, you can't rely on two "equals" DataLayout
having the same string returned by getStringRepresentation().

Get rid of DataLayoutPass: the DataLayout is in the Module

The DataLayout is "per-module", let's enforce this by not
duplicating it more than necessary.
One more step toward non-optionality of the DataLayout in the
module.

Make DataLayout Non-Optional in the Module

Module->getDataLayout() will never returns nullptr anymore.

Reviewers: echristo

Subscribers: resistor, llvm-commits, jholewinski

Differential Revision: http://reviews.llvm.org/D7992

From: Mehdi Amini <mehdi.amini@apple.com>

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@231270 91177308-0d34-0410-b5e6-96231b3b80d8
2015-03-04 18:43:29 +00:00
..

//===----------------------------------------------------------------------===/
//                 Kaleidoscope with Orc - Lazy IRGen Version
//===----------------------------------------------------------------------===//

This version of Kaleidoscope with Orc demonstrates fully lazy IR-generation.
Building on the lazy-irgen version of the tutorial, this version injects JIT
callbacks to defer the bulk of IR-generation and code-generation of functions until
they are first called.

When a function definition is entered, a JIT callback is created and a stub
function is built that will call the body of the function indirectly. The body of
the function is *not* IRGen'd at this point. Instead, the function pointer for
the indirect call is initialized to point at the JIT callback, and the compile
action for the callback is initialized with a lambda that IRGens the body of the
function and adds it to the JIT. The function pointer is updated by the JIT
callback's update action to point at the newly emitted function body, so future
calls to the stub will go straight to the body, not through the JIT.

This directory contains a Makefile that allows 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.