summaryrefslogtreecommitdiffstats
path: root/llvm/docs/tutorial/LangImpl1.rst
Commit message (Collapse)AuthorAgeFilesLines
* New Kaleidoscope chapter: Creating object filesWilfred Hughes2016-07-021-290/+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
* Fix some typos in the Kaleidoscope tutorial (PR28120)Hans Wennborg2016-06-141-1/+1
| | | | llvm-svn: 272681
* LLVM tutorial: fix broken links/anchorsAlex Denisov2015-12-151-2/+2
| | | | llvm-svn: 255671
* [Kaleidoscope] Clang-format the Kaleidoscope tutorials.Lang Hames2015-08-191-7/+12
| | | | | | Also reduces changes between tutorial chapters. llvm-svn: 245472
* [Kaleidoscope] Start C++11'ifying the kaleidoscope tutorials.Lang Hames2015-08-181-1/+1
| | | | llvm-svn: 245322
* Fixup debug information references.Charlie Turner2015-01-241-1/+8
| | | | llvm-svn: 227020
* Update references to lines of code count.Charlie Turner2015-01-241-1/+1
| | | | | | | | The number of lines of code in Kaleidoscope has risen from the previously reported 700 to 986 according to the cloc tool. This tools was run on the toy.cpp file from Chapter 8. llvm-svn: 227019
* Fix spellingNikola Smiljanic2013-05-011-1/+1
| | | | llvm-svn: 180843
* [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/+280
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