<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>1. Kaleidoscope: Tutorial Introduction and the Lexer — LLVM 8 documentation</title>
<link rel="stylesheet" href="../_static/llvm-theme.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<script type="text/javascript" id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<script type="text/javascript" src="../_static/language_data.js"></script>
<link rel="index" title="Index" href="../genindex.html" />
<link rel="search" title="Search" href="../search.html" />
<link rel="next" title="2. Kaleidoscope: Implementing a Parser and AST" href="OCamlLangImpl2.html" />
<link rel="prev" title="10. Kaleidoscope: Conclusion and other useful LLVM tidbits" href="LangImpl10.html" />
<style type="text/css">
table.right { float: right; margin-left: 20px; }
table.right td { border: 1px solid #ccc; }
</style>
</head><body>
<div class="logo">
<a href="../index.html">
<img src="../_static/logo.png"
alt="LLVM Logo" width="250" height="88"/></a>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="../genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="OCamlLangImpl2.html" title="2. Kaleidoscope: Implementing a Parser and AST"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="LangImpl10.html" title="10. Kaleidoscope: Conclusion and other useful LLVM tidbits"
accesskey="P">previous</a> |</li>
<li><a href="http://llvm.org/">LLVM Home</a> | </li>
<li><a href="../index.html">Documentation</a>»</li>
<li class="nav-item nav-item-1"><a href="index.html" accesskey="U">LLVM Tutorial: Table of Contents</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="body" role="main">
<div class="section" id="kaleidoscope-tutorial-introduction-and-the-lexer">
<h1>1. Kaleidoscope: Tutorial Introduction and the Lexer<a class="headerlink" href="#kaleidoscope-tutorial-introduction-and-the-lexer" title="Permalink to this headline">¶</a></h1>
<div class="contents local topic" id="contents">
<ul class="simple">
<li><a class="reference internal" href="#tutorial-introduction" id="id1">Tutorial Introduction</a></li>
<li><a class="reference internal" href="#the-basic-language" id="id2">The Basic Language</a></li>
<li><a class="reference internal" href="#the-lexer" id="id3">The Lexer</a></li>
</ul>
</div>
<div class="section" id="tutorial-introduction">
<h2><a class="toc-backref" href="#id1">1.1. Tutorial Introduction</a><a class="headerlink" href="#tutorial-introduction" title="Permalink to this headline">¶</a></h2>
<p>Welcome to the “Implementing a language with LLVM” tutorial. This
tutorial runs through the implementation of a simple language, showing
how fun and easy it can be. This tutorial will get you up and started as
well as help to build a framework you can extend to other languages. The
code in this tutorial can also be used as a playground to hack on other
LLVM specific things.</p>
<p>The goal of this tutorial is to progressively unveil our language,
describing how it is built up over time. This will let us cover a fairly
broad range of language design and LLVM-specific usage issues, showing
and explaining the code for it all along the way, without overwhelming
you with tons of details up front.</p>
<p>It is useful to point out ahead of time that this tutorial is really
about teaching compiler techniques and LLVM specifically, <em>not</em> about
teaching modern and sane software engineering principles. In practice,
this means that we’ll take a number of shortcuts to simplify the
exposition. For example, the code leaks memory, uses global variables
all over the place, doesn’t use nice design patterns like
<a class="reference external" href="http://en.wikipedia.org/wiki/Visitor_pattern">visitors</a>, etc… but
it is very simple. If you dig in and use the code as a basis for future
projects, fixing these deficiencies shouldn’t be hard.</p>
<p>I’ve tried to put this tutorial together in a way that makes chapters
easy to skip over if you are already familiar with or are uninterested
in the various pieces. The structure of the tutorial is:</p>
<ul class="simple">
<li><a class="reference external" href="#language">Chapter #1</a>: Introduction to the Kaleidoscope
language, and the definition of its Lexer - This shows where we are
going and the basic functionality that we want it to do. In order to
make this tutorial maximally understandable and hackable, we choose
to implement everything in Objective Caml instead of using lexer and
parser generators. LLVM obviously works just fine with such tools,
feel free to use one if you prefer.</li>
<li><a class="reference external" href="OCamlLangImpl2.html">Chapter #2</a>: Implementing a Parser and
AST - With the lexer in place, we can talk about parsing techniques
and basic AST construction. This tutorial describes recursive descent
parsing and operator precedence parsing. Nothing in Chapters 1 or 2
is LLVM-specific, the code doesn’t even link in LLVM at this point.
:)</li>
<li><a class="reference external" href="OCamlLangImpl3.html">Chapter #3</a>: Code generation to LLVM IR -
With the AST ready, we can show off how easy generation of LLVM IR
really is.</li>
<li><a class="reference external" href="OCamlLangImpl4.html">Chapter #4</a>: Adding JIT and Optimizer
Support - Because a lot of people are interested in using LLVM as a
JIT, we’ll dive right into it and show you the 3 lines it takes to
add JIT support. LLVM is also useful in many other ways, but this is
one simple and “sexy” way to shows off its power. :)</li>
<li><a class="reference external" href="OCamlLangImpl5.html">Chapter #5</a>: Extending the Language:
Control Flow - With the language up and running, we show how to
extend it with control flow operations (if/then/else and a ‘for’
loop). This gives us a chance to talk about simple SSA construction
and control flow.</li>
<li><a class="reference external" href="OCamlLangImpl6.html">Chapter #6</a>: Extending the Language:
User-defined Operators - This is a silly but fun chapter that talks
about extending the language to let the user program define their own
arbitrary unary and binary operators (with assignable precedence!).
This lets us build a significant piece of the “language” as library
routines.</li>
<li><a class="reference external" href="OCamlLangImpl7.html">Chapter #7</a>: Extending the Language:
Mutable Variables - This chapter talks about adding user-defined
local variables along with an assignment operator. The interesting
part about this is how easy and trivial it is to construct SSA form
in LLVM: no, LLVM does <em>not</em> require your front-end to construct SSA
form!</li>
<li><a class="reference external" href="OCamlLangImpl8.html">Chapter #8</a>: Conclusion and other useful
LLVM tidbits - This chapter wraps up the series by talking about
potential ways to extend the language, but also includes a bunch of
pointers to info about “special topics” like adding garbage
collection support, exceptions, debugging, support for “spaghetti
stacks”, and a bunch of other tips and tricks.</li>
</ul>
<p>By the end of the tutorial, we’ll have written a bit less than 700 lines
of non-comment, non-blank, lines of code. With this small amount of
code, we’ll have built up a very reasonable compiler for a non-trivial
language including a hand-written lexer, parser, AST, as well as code
generation support with a JIT compiler. While other systems may have
interesting “hello world” tutorials, I think the breadth of this
tutorial is a great testament to the strengths of LLVM and why you
should consider it if you’re interested in language or compiler design.</p>
<p>A note about this tutorial: we expect you to extend the language and
play with it on your own. Take the code and go crazy hacking away at it,
compilers don’t need to be scary creatures - it can be a lot of fun to
play with languages!</p>
</div>
<div class="section" id="the-basic-language">
<h2><a class="toc-backref" href="#id2">1.2. The Basic Language</a><a class="headerlink" href="#the-basic-language" title="Permalink to this headline">¶</a></h2>
<p>This tutorial will be illustrated with a toy language that we’ll call
“<a class="reference external" href="http://en.wikipedia.org/wiki/Kaleidoscope">Kaleidoscope</a>” (derived
from “meaning beautiful, form, and view”). Kaleidoscope is a procedural
language that allows you to define functions, use conditionals, math,
etc. Over the course of the tutorial, we’ll extend Kaleidoscope to
support the if/then/else construct, a for loop, user defined operators,
JIT compilation with a simple command line interface, etc.</p>
<p>Because we want to keep things simple, the only datatype in Kaleidoscope
is a 64-bit floating point type (aka ‘float’ in OCaml parlance). As
such, all values are implicitly double precision and the language
doesn’t require type declarations. This gives the language a very nice
and simple syntax. For example, the following simple example computes
<a class="reference external" href="http://en.wikipedia.org/wiki/Fibonacci_number">Fibonacci numbers:</a></p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># Compute the x'th fibonacci number.</span>
<span class="k">def</span> <span class="nf">fib</span><span class="p">(</span><span class="n">x</span><span class="p">)</span>
<span class="k">if</span> <span class="n">x</span> <span class="o"><</span> <span class="mi">3</span> <span class="n">then</span>
<span class="mi">1</span>
<span class="k">else</span>
<span class="n">fib</span><span class="p">(</span><span class="n">x</span><span class="o">-</span><span class="mi">1</span><span class="p">)</span><span class="o">+</span><span class="n">fib</span><span class="p">(</span><span class="n">x</span><span class="o">-</span><span class="mi">2</span><span class="p">)</span>
<span class="c1"># This expression will compute the 40th number.</span>
<span class="n">fib</span><span class="p">(</span><span class="mi">40</span><span class="p">)</span>
</pre></div>
</div>
<p>We also allow Kaleidoscope to call into standard library functions (the
LLVM JIT makes this completely trivial). This means that you can use the
‘extern’ keyword to define a function before you use it (this is also
useful for mutually recursive functions). For example:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">extern</span> <span class="n">sin</span><span class="p">(</span><span class="n">arg</span><span class="p">);</span>
<span class="n">extern</span> <span class="n">cos</span><span class="p">(</span><span class="n">arg</span><span class="p">);</span>
<span class="n">extern</span> <span class="n">atan2</span><span class="p">(</span><span class="n">arg1</span> <span class="n">arg2</span><span class="p">);</span>
<span class="n">atan2</span><span class="p">(</span><span class="n">sin</span><span class="p">(</span><span class="o">.</span><span class="mi">4</span><span class="p">),</span> <span class="n">cos</span><span class="p">(</span><span class="mi">42</span><span class="p">))</span>
</pre></div>
</div>
<p>A more interesting example is included in Chapter 6 where we write a
little Kaleidoscope application that <a class="reference external" href="OCamlLangImpl6.html#kicking-the-tires">displays a Mandelbrot
Set</a> at various levels of magnification.</p>
<p>Lets dive into the implementation of this language!</p>
</div>
<div class="section" id="the-lexer">
<h2><a class="toc-backref" href="#id3">1.3. The Lexer</a><a class="headerlink" href="#the-lexer" title="Permalink to this headline">¶</a></h2>
<p>When it comes to implementing a language, the first thing needed is the
ability to process a text file and recognize what it says. The
traditional way to do this is to use a
“<a class="reference external" href="http://en.wikipedia.org/wiki/Lexical_analysis">lexer</a>” (aka
‘scanner’) to break the input up into “tokens”. Each token returned by
the lexer includes a token code and potentially some metadata (e.g. the
numeric value of a number). First, we define the possibilities:</p>
<div class="highlight-ocaml notranslate"><div class="highlight"><pre><span></span><span class="c">(* The lexer returns these 'Kwd' if it is an unknown character, otherwise one of</span>
<span class="c"> * these others for known things. *)</span>
<span class="k">type</span> <span class="n">token</span> <span class="o">=</span>
<span class="c">(* commands *)</span>
<span class="o">|</span> <span class="nc">Def</span> <span class="o">|</span> <span class="nc">Extern</span>
<span class="c">(* primary *)</span>
<span class="o">|</span> <span class="nc">Ident</span> <span class="k">of</span> <span class="kt">string</span> <span class="o">|</span> <span class="nc">Number</span> <span class="k">of</span> <span class="kt">float</span>
<span class="c">(* unknown *)</span>
<span class="o">|</span> <span class="nc">Kwd</span> <span class="k">of</span> <span class="kt">char</span>
</pre></div>
</div>
<p>Each token returned by our lexer will be one of the token variant
values. An unknown character like ‘+’ will be returned as
<code class="docutils literal notranslate"><span class="pre">Token.Kwd</span> <span class="pre">'+'</span></code>. If the curr token is an identifier, the value will be
<code class="docutils literal notranslate"><span class="pre">Token.Ident</span> <span class="pre">s</span></code>. If the current token is a numeric literal (like 1.0),
the value will be <code class="docutils literal notranslate"><span class="pre">Token.Number</span> <span class="pre">1.0</span></code>.</p>
<p>The actual implementation of the lexer is a collection of functions
driven by a function named <code class="docutils literal notranslate"><span class="pre">Lexer.lex</span></code>. The <code class="docutils literal notranslate"><span class="pre">Lexer.lex</span></code> function is
called to return the next token from standard input. We will use
<a class="reference external" href="http://caml.inria.fr/pub/docs/manual-camlp4/index.html">Camlp4</a> to
simplify the tokenization of the standard input. Its definition starts
as:</p>
<div class="highlight-ocaml notranslate"><div class="highlight"><pre><span></span><span class="c">(*===----------------------------------------------------------------------===</span>
<span class="c"> * Lexer</span>
<span class="c"> *===----------------------------------------------------------------------===*)</span>
<span class="k">let</span> <span class="k">rec</span> <span class="n">lex</span> <span class="o">=</span> <span class="n">parser</span>
<span class="c">(* Skip any whitespace. *)</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span> <span class="o">(</span><span class="sc">' '</span> <span class="o">|</span> <span class="sc">'\n'</span> <span class="o">|</span> <span class="sc">'\r'</span> <span class="o">|</span> <span class="sc">'\t'</span><span class="o">);</span> <span class="n">stream</span> <span class="o">>]</span> <span class="o">-></span> <span class="n">lex</span> <span class="n">stream</span>
</pre></div>
</div>
<p><code class="docutils literal notranslate"><span class="pre">Lexer.lex</span></code> works by recursing over a <code class="docutils literal notranslate"><span class="pre">char</span> <span class="pre">Stream.t</span></code> to read
characters one at a time from the standard input. It eats them as it
recognizes them and stores them in a <code class="docutils literal notranslate"><span class="pre">Token.token</span></code> variant. The
first thing that it has to do is ignore whitespace between tokens. This
is accomplished with the recursive call above.</p>
<p>The next thing <code class="docutils literal notranslate"><span class="pre">Lexer.lex</span></code> needs to do is recognize identifiers and
specific keywords like “def”. Kaleidoscope does this with a pattern
match and a helper function.</p>
<div class="highlight-ocaml notranslate"><div class="highlight"><pre><span></span> <span class="c">(* identifier: [a-zA-Z][a-zA-Z0-9] *)</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span> <span class="o">(</span><span class="sc">'A'</span> <span class="o">..</span> <span class="sc">'Z'</span> <span class="o">|</span> <span class="sc">'a'</span> <span class="o">..</span> <span class="sc">'z'</span> <span class="k">as</span> <span class="n">c</span><span class="o">);</span> <span class="n">stream</span> <span class="o">>]</span> <span class="o">-></span>
<span class="k">let</span> <span class="n">buffer</span> <span class="o">=</span> <span class="nn">Buffer</span><span class="p">.</span><span class="n">create</span> <span class="mi">1</span> <span class="k">in</span>
<span class="nn">Buffer</span><span class="p">.</span><span class="n">add_char</span> <span class="n">buffer</span> <span class="n">c</span><span class="o">;</span>
<span class="n">lex_ident</span> <span class="n">buffer</span> <span class="n">stream</span>
<span class="o">...</span>
<span class="ow">and</span> <span class="n">lex_ident</span> <span class="n">buffer</span> <span class="o">=</span> <span class="n">parser</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span> <span class="o">(</span><span class="sc">'A'</span> <span class="o">..</span> <span class="sc">'Z'</span> <span class="o">|</span> <span class="sc">'a'</span> <span class="o">..</span> <span class="sc">'z'</span> <span class="o">|</span> <span class="sc">'0'</span> <span class="o">..</span> <span class="sc">'9'</span> <span class="k">as</span> <span class="n">c</span><span class="o">);</span> <span class="n">stream</span> <span class="o">>]</span> <span class="o">-></span>
<span class="nn">Buffer</span><span class="p">.</span><span class="n">add_char</span> <span class="n">buffer</span> <span class="n">c</span><span class="o">;</span>
<span class="n">lex_ident</span> <span class="n">buffer</span> <span class="n">stream</span>
<span class="o">|</span> <span class="o">[<</span> <span class="n">stream</span><span class="o">=</span><span class="n">lex</span> <span class="o">>]</span> <span class="o">-></span>
<span class="k">match</span> <span class="nn">Buffer</span><span class="p">.</span><span class="n">contents</span> <span class="n">buffer</span> <span class="k">with</span>
<span class="o">|</span> <span class="s2">"def"</span> <span class="o">-></span> <span class="o">[<</span> <span class="k">'</span><span class="nn">Token</span><span class="p">.</span><span class="nc">Def</span><span class="o">;</span> <span class="n">stream</span> <span class="o">>]</span>
<span class="o">|</span> <span class="s2">"extern"</span> <span class="o">-></span> <span class="o">[<</span> <span class="k">'</span><span class="nn">Token</span><span class="p">.</span><span class="nc">Extern</span><span class="o">;</span> <span class="n">stream</span> <span class="o">>]</span>
<span class="o">|</span> <span class="n">id</span> <span class="o">-></span> <span class="o">[<</span> <span class="k">'</span><span class="nn">Token</span><span class="p">.</span><span class="nc">Ident</span> <span class="n">id</span><span class="o">;</span> <span class="n">stream</span> <span class="o">>]</span>
</pre></div>
</div>
<p>Numeric values are similar:</p>
<div class="highlight-ocaml notranslate"><div class="highlight"><pre><span></span> <span class="c">(* number: [0-9.]+ *)</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span> <span class="o">(</span><span class="sc">'0'</span> <span class="o">..</span> <span class="sc">'9'</span> <span class="k">as</span> <span class="n">c</span><span class="o">);</span> <span class="n">stream</span> <span class="o">>]</span> <span class="o">-></span>
<span class="k">let</span> <span class="n">buffer</span> <span class="o">=</span> <span class="nn">Buffer</span><span class="p">.</span><span class="n">create</span> <span class="mi">1</span> <span class="k">in</span>
<span class="nn">Buffer</span><span class="p">.</span><span class="n">add_char</span> <span class="n">buffer</span> <span class="n">c</span><span class="o">;</span>
<span class="n">lex_number</span> <span class="n">buffer</span> <span class="n">stream</span>
<span class="o">...</span>
<span class="ow">and</span> <span class="n">lex_number</span> <span class="n">buffer</span> <span class="o">=</span> <span class="n">parser</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span> <span class="o">(</span><span class="sc">'0'</span> <span class="o">..</span> <span class="sc">'9'</span> <span class="o">|</span> <span class="sc">'.'</span> <span class="k">as</span> <span class="n">c</span><span class="o">);</span> <span class="n">stream</span> <span class="o">>]</span> <span class="o">-></span>
<span class="nn">Buffer</span><span class="p">.</span><span class="n">add_char</span> <span class="n">buffer</span> <span class="n">c</span><span class="o">;</span>
<span class="n">lex_number</span> <span class="n">buffer</span> <span class="n">stream</span>
<span class="o">|</span> <span class="o">[<</span> <span class="n">stream</span><span class="o">=</span><span class="n">lex</span> <span class="o">>]</span> <span class="o">-></span>
<span class="o">[<</span> <span class="k">'</span><span class="nn">Token</span><span class="p">.</span><span class="nc">Number</span> <span class="o">(</span><span class="n">float_of_string</span> <span class="o">(</span><span class="nn">Buffer</span><span class="p">.</span><span class="n">contents</span> <span class="n">buffer</span><span class="o">));</span> <span class="n">stream</span> <span class="o">>]</span>
</pre></div>
</div>
<p>This is all pretty straight-forward code for processing input. When
reading a numeric value from input, we use the ocaml <code class="docutils literal notranslate"><span class="pre">float_of_string</span></code>
function to convert it to a numeric value that we store in
<code class="docutils literal notranslate"><span class="pre">Token.Number</span></code>. Note that this isn’t doing sufficient error checking:
it will raise <code class="docutils literal notranslate"><span class="pre">Failure</span></code> if the string “1.23.45.67”. Feel free to
extend it :). Next we handle comments:</p>
<div class="highlight-ocaml notranslate"><div class="highlight"><pre><span></span> <span class="c">(* Comment until end of line. *)</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span> <span class="o">(</span><span class="sc">'#'</span><span class="o">);</span> <span class="n">stream</span> <span class="o">>]</span> <span class="o">-></span>
<span class="n">lex_comment</span> <span class="n">stream</span>
<span class="o">...</span>
<span class="ow">and</span> <span class="n">lex_comment</span> <span class="o">=</span> <span class="n">parser</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span> <span class="o">(</span><span class="sc">'\n'</span><span class="o">);</span> <span class="n">stream</span><span class="o">=</span><span class="n">lex</span> <span class="o">>]</span> <span class="o">-></span> <span class="n">stream</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span><span class="n">c</span><span class="o">;</span> <span class="n">e</span><span class="o">=</span><span class="n">lex_comment</span> <span class="o">>]</span> <span class="o">-></span> <span class="n">e</span>
<span class="o">|</span> <span class="o">[<</span> <span class="o">>]</span> <span class="o">-></span> <span class="o">[<</span> <span class="o">>]</span>
</pre></div>
</div>
<p>We handle comments by skipping to the end of the line and then return
the next token. Finally, if the input doesn’t match one of the above
cases, it is either an operator character like ‘+’ or the end of the
file. These are handled with this code:</p>
<div class="highlight-ocaml notranslate"><div class="highlight"><pre><span></span><span class="c">(* Otherwise, just return the character as its ascii value. *)</span>
<span class="o">|</span> <span class="o">[<</span> <span class="k">'</span><span class="n">c</span><span class="o">;</span> <span class="n">stream</span> <span class="o">>]</span> <span class="o">-></span>
<span class="o">[<</span> <span class="k">'</span><span class="nn">Token</span><span class="p">.</span><span class="nc">Kwd</span> <span class="n">c</span><span class="o">;</span> <span class="n">lex</span> <span class="n">stream</span> <span class="o">>]</span>
<span class="c">(* end of stream. *)</span>
<span class="o">|</span> <span class="o">[<</span> <span class="o">>]</span> <span class="o">-></span> <span class="o">[<</span> <span class="o">>]</span>
</pre></div>
</div>
<p>With this, we have the complete lexer for the basic Kaleidoscope
language (the <a class="reference external" href="OCamlLangImpl2.html#full-code-listing">full code listing</a> for the
Lexer is available in the <a class="reference external" href="OCamlLangImpl2.html">next chapter</a> of the
tutorial). Next we’ll <a class="reference external" href="OCamlLangImpl2.html">build a simple parser that uses this to build an
Abstract Syntax Tree</a>. When we have that, we’ll
include a driver so that you can use the lexer and parser together.</p>
<p><a class="reference external" href="OCamlLangImpl2.html">Next: Implementing a Parser and AST</a></p>
</div>
</div>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="../genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="OCamlLangImpl2.html" title="2. Kaleidoscope: Implementing a Parser and AST"
>next</a> |</li>
<li class="right" >
<a href="LangImpl10.html" title="10. Kaleidoscope: Conclusion and other useful LLVM tidbits"
>previous</a> |</li>
<li><a href="http://llvm.org/">LLVM Home</a> | </li>
<li><a href="../index.html">Documentation</a>»</li>
<li class="nav-item nav-item-1"><a href="index.html" >LLVM Tutorial: Table of Contents</a> »</li>
</ul>
</div>
<div class="footer" role="contentinfo">
© Copyright 2003-2020, LLVM Project.
Last updated on 2020-09-07.
Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.8.4.
</div>
</body>
</html>
distrib
>
Mageia
>
7
>
i586
>
media
>
core-updates
>
by-pkgid
>
d635a8cd705396ade48f1d2b830a115d
>
files
>
2611
