summaryrefslogtreecommitdiffstats
path: root/llvm/docs/tutorial/LangImpl4.rst
Commit message (Collapse)AuthorAgeFilesLines
* New Kaleidoscope chapter: Creating object filesWilfred Hughes2016-07-021-610/+0
| | | | | | | | | | | | This new chapter describes compiling LLVM IR to object files. The new chaper is chapter 8, so later chapters have been renumbered. Since this brings us to 10 chapters total, I've also needed to rename the other chapters to use two digit numbering. Differential Revision: http://reviews.llvm.org/D18070 llvm-svn: 274441
* Remove every uses of getGlobalContext() in LLVM (but the C API)Mehdi Amini2016-04-141-1/+2
| | | | | | | | | | | At the same time, fixes InstructionsTest::CastInst unittest: yes you can leave the IR in an invalid state and exit when you don't destroy the context (like the global one), no longer now. This is the first part of http://reviews.llvm.org/D19094 From: Mehdi Amini <mehdi.amini@apple.com> llvm-svn: 266379
* LLVM tutorial: fix broken links/anchorsAlex Denisov2015-12-151-2/+2
| | | | llvm-svn: 255671
* Recommit r246175 - Add Kaleidoscope regression tests, with a fix to make sureLang Hames2015-08-271-1/+1
| | | | | | the kaleidoscope 'library' functions aren't dead-stripped in release builds. llvm-svn: 246201
* Revert r246175 to get builder green again.Lang Hames2015-08-271-1/+1
| | | | llvm-svn: 246185
* Add Kaleidoscope regression tests.Lang Hames2015-08-271-1/+1
| | | | | | These will be run if LLVM_BUILD_EXAMPLES is enabled. llvm-svn: 246175
* Big Kaleidoscope tutorial update.Lang Hames2015-08-261-93/+258
| | | | | | | | | | | | | This commit switches the underlying JIT for the Kaleidoscope tutorials from MCJIT to a custom ORC-based JIT, KaleidoscopeJIT. This fixes a lot of the bugs in Kaleidoscope that were introduced when we deleted the legacy JIT. The documentation for Chapter 4, which introduces the JIT APIs, is updated to reflect the change. Also included are a number of C++11 modernizations and general cleanup. Where appropriate, the docs have been updated to reflect these changes too. llvm-svn: 246002
* [Kaleidoscope] Clang-format the Kaleidoscope tutorials.Lang Hames2015-08-191-2/+1
| | | | | | Also reduces changes between tutorial chapters. llvm-svn: 245472
* [Kaleidoscope] Start C++11'ifying the kaleidoscope tutorials.Lang Hames2015-08-181-4/+4
| | | | llvm-svn: 245322
* The Kaleidoscope tutorial should be using "mcjit" for the library,Eric Christopher2015-01-081-1/+1
| | | | | | "jit" doesn't exist anymore. llvm-svn: 225462
* [Docs][JIT] Update the clang++ invocation lines in the kaleidoscope docs.Lang Hames2014-11-061-1/+1
| | | | | | | The old examples had missing/incorrect flags that were causing failures on newer versions of clang and the tutorial code. llvm-svn: 221419
* Update code listings in LLVM tutorial.Logan Chien2013-06-081-618/+2
| | | | | | | | | | | Several LLVM headers are moved. The code listings in LLVM tutorial are not updated yet. This CL removes the code replica in the .rst, and replace them with a literalinclude directive, so that sphinx can include the latest code automatically. llvm-svn: 183607
* [docs] Remove explicit authorship.Sean Silva2013-03-111-2/+0
| | | | | | | In the spirit of r172109. Version control keeps a far more detailed record of authorship anyways. llvm-svn: 176807
* docs: Sphinxify `docs/tutorial/`Sean Silva2012-12-051-0/+1063
Sorry for the massive commit, but I just wanted to knock this one down and it is really straightforward. There are still a couple trivial (i.e. not related to the content) things left to fix: - Use of raw HTML links where :doc:`...` and :ref:`...` could be used instead. If you are a newbie and want to help fix this it would make for some good bite-sized patches; more experienced developers should be focusing on adding new content (to this tutorial or elsewhere, but please _do not_ waste your time on formatting when there is such dire need for documentation (see docs/SphinxQuickstartTemplate.rst to get started writing)). - Highlighting of the kaleidoscope code blocks (currently left as bare `::`). I will be working on writing a custom Pygments highlighter for this, mostly as training for maintaining the `llvm` code-block's lexer in-tree. I want to do this because I am extremely unhappy with how it just "gives up" on the slightest deviation from the expected syntax and leaves the whole code-block un-highlighted. More generally I am looking at writing some Sphinx extensions and keeping them in-tree as well, to support common use cases that currently have no good solution (like "monospace text inside a link"). llvm-svn: 169343
OpenPOWER on IntegriCloud