- Nov 04, 2016
-
-
Ahmed Bougacha authored
This reflects the current state of Global ISel. As progress is made, we'll document our design decisions in it. Comments very welcome! llvm-svn: 286002
-
- Oct 13, 2016
-
-
Mehdi Amini authored
This document describes the proposal to move to GitHub, and compare the two proposals through various workflow examples, presenting the current set of commands following by the ones involved in each of the two proposals. It is intended to supersede the previous "submodule proposal" document entirely, and drive the discussion at the BoF during the next Dev Meeting. Differential Revision: https://reviews.llvm.org/D24167 llvm-svn: 284077
-
- Aug 27, 2016
-
-
Andrew Kaylor authored
llvm-svn: 279881
-
- Aug 17, 2016
-
-
George Burgess IV authored
Patch partially by Danny. Differential Revision: https://reviews.llvm.org/D23535 llvm-svn: 278875
-
- Jul 23, 2016
-
-
David Majnemer authored
This is the first patch in the coroutine series. It contains the documentation for the coroutine intrinsics and their usage. Patch by Gor Nishanov! Differential Revision: https://reviews.llvm.org/D22603 llvm-svn: 276513
-
- Jul 21, 2016
-
-
Renato Golin authored
Given that other proposals are making their way through, it's better if we specify what GitHub proposal this is, in case there are others that also involve GitHub, but not sub-modules. llvm-svn: 276325
-
- Jul 20, 2016
-
-
Renato Golin authored
llvm-svn: 276099
-
- Jun 30, 2016
-
-
Chandler Carruth authored
associated reporting guide. I want to emphasize that at this point these are just drafts! This is the result of very extended discussion on the mailing lists on several different threads: http://lists.llvm.org/pipermail/llvm-dev/2015-October/091218.html http://lists.llvm.org/pipermail/llvm-dev/2016-May/099120.html http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20151019/307070.html The reporting guide in particular I anticipate will be shaped somewhat by the advisory committee when they are selected. But hopefully this serves as a good starting point and good guidance while the advisory committee is being sorted out. I'd like to thank all the folks who contributed to this. Many, *many* people worked to help with drafting, wording, suggestions, and edits. Also, this is based on widely used existing codes of coduct as mentioned in the text, and the original authors of those deserve many thanks as well. Differential Revision: http://reviews.llvm.org/D13741 llvm-svn: 274268
-
- Jun 24, 2016
-
-
Peter Collingbourne authored
The bitset metadata currently used in LLVM has a few problems: 1. It has the wrong name. The name "bitset" refers to an implementation detail of one use of the metadata (i.e. its original use case, CFI). This makes it harder to understand, as the name makes no sense in the context of virtual call optimization. 2. It is represented using a global named metadata node, rather than being directly associated with a global. This makes it harder to manipulate the metadata when rebuilding global variables, summarise it as part of ThinLTO and drop unused metadata when associated globals are dropped. For this reason, CFI does not currently work correctly when both CFI and vcall opt are enabled, as vcall opt needs to rebuild vtable globals, and fails to associate metadata with the rebuilt globals. As I understand it, the same problem could also affect ASan, which rebuilds globals with a red zone. This patch solves both of those problems in the following way: 1. Rename the metadata to "type metadata". This new name reflects how the metadata is currently being used (i.e. to represent type information for CFI and vtable opt). The new name is reflected in the name for the associated intrinsic (llvm.type.test) and pass (LowerTypeTests). 2. Attach metadata directly to the globals that it pertains to, rather than using the "llvm.bitsets" global metadata node as we are doing now. This is done using the newly introduced capability to attach metadata to global variables (r271348 and r271358). See also: http://lists.llvm.org/pipermail/llvm-dev/2016-June/100462.html Differential Revision: http://reviews.llvm.org/D21053 llvm-svn: 273729
-
- Jun 08, 2016
-
-
Kostya Serebryany authored
[docs] fix the build by including ScudoHardenedAllocator into toc; mention SourceBasedCodeCoverage.html in libFuzzer docs llvm-svn: 272070
-
- Apr 29, 2016
-
-
Chris Bieneman authored
This document is intended to provide a basic overview of the CMake scripting language for LLVM developers. It was unorthodoxly reviewed for accuracy and content on the CMake developer list: http://public.kitware.com/pipermail/cmake-developers/2016-April/028300.html llvm-svn: 268096
-
- Mar 18, 2016
-
-
Chris Bieneman authored
* Renamed to be camel case, consistent with other docs. * Fixed non-ascii characters (this is what I get for writing docs on an iPad). llvm-svn: 263840
-
Chris Bieneman authored
This document covers how to use some of the new complex build configurations CMake supports. Feedback and improvements welcomed! llvm-svn: 263834
-
- Jan 30, 2016
-
-
Alexey Samsonov authored
llvm-svn: 259280
-
- Jan 26, 2016
-
-
Chris Bieneman authored
I broke the documentation builds when I deleted the MakefileGuide as part of the autoconf removal. At some point I'll need to do a more in-depth pass updating the documentation to remove references to the old build system. llvm-svn: 258873
-
- Nov 10, 2015
-
-
Jingyue Wu authored
Summary: This patch adds documentation on compiling CUDA with LLVM as requested by many engineers and researchers. It includes not only user guides but also some internals (mostly optimizations) so that early adopters can start hacking and contributing. Quite a few researchers who contacted us haven't used LLVM before, which is unsurprising as it hasn't been long since LLVM picked up CUDA. So I added a short summary to help these folks get started with LLVM. I expect this document to evolve substantially down the road. The user guides will be much simplified after the Clang integration is done. However, the internals should continue growing to include for example performance debugging and key areas to improve. Reviewers: chandlerc, meheff, broune, tra Subscribers: silvas, jingyue, llvm-commits, eliben Differential Revision: http://reviews.llvm.org/D14370 llvm-svn: 252660
-
- Aug 07, 2015
-
-
Alex Lorenz authored
Differential Revision: http://reviews.llvm.org/D11736 llvm-svn: 244292
-
- Aug 05, 2015
-
-
Tanya Lattner authored
llvm-svn: 243999
-
- Jun 15, 2015
-
-
Sanjoy Das authored
Add FaultMaps.rst to toctree. llvm-svn: 239747
-
- Jun 13, 2015
-
-
Tom Stellard authored
llvm-svn: 239657
-
- Mar 31, 2015
-
-
Kostya Serebryany authored
Summary: Move lib/Fuzzer docs from a README.txt to a proper .rst file. This change does not add any content, just formatting. Test Plan: n/a Reviewers: samsonov Reviewed By: samsonov Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D8710 llvm-svn: 233638
-
- Mar 13, 2015
-
-
Chris Bieneman authored
Reviewers: chandlerc, samsonov, echristo Reviewed By: samsonov Subscribers: emaste, joker.eph, llvm-commits Differential Revision: http://reviews.llvm.org/D8046 llvm-svn: 232135
-
- Feb 28, 2015
-
-
Philip Reames authored
As mentioned on llvm-dev, this is a new documentation page intended to collect tips for frontend authors on how to generate IR that LLVM is able to optimize well. These types of things come up repeated in review threads and it would be good to have a place to save them. I added a small handful to start us off, but I mostly want to get the framework in place. Once the docs are here, we can add to them incrementally. If you know of something appropriate for this page, please add it! Differential Revision: http://reviews.llvm.org/D7890 llvm-svn: 230807
-
- Feb 20, 2015
-
-
Peter Collingbourne authored
This patch introduces a new mechanism that allows IR modules to co-operatively build pointer sets corresponding to addresses within a given set of globals. One particular use case for this is to allow a C++ program to efficiently verify (at each call site) that a vtable pointer is in the set of valid vtable pointers for the class or its derived classes. One way of doing this is for a toolchain component to build, for each class, a bit set that maps to the memory region allocated for the vtables, such that each 1 bit in the bit set maps to a valid vtable for that class, and lay out the vtables next to each other, to minimize the total size of the bit sets. The patch introduces a metadata format for representing pointer sets, an '@llvm.bitset.test' intrinsic and an LTO lowering pass that lays out the globals and builds the bitsets, and documents the new feature. Differential Revision: http://reviews.llvm.org/D7288 llvm-svn: 230054
-
- Feb 04, 2015
-
-
Sean Silva authored
llvm-svn: 228192
-
- Jan 13, 2015
-
-
Peter Collingbourne authored
llvm-svn: 225815
-
- Dec 10, 2014
-
-
Stepan Dyatkovskiy authored
Pass looks for equivalent functions that are mergable and folds them. llvm-svn: 223931
-
- Dec 03, 2014
-
-
Matt Arsenault authored
It was complaining it wasn't included in any toctree llvm-svn: 223254
-
- Nov 14, 2014
-
-
Tom Stellard authored
This was done using the Sparc and PowerPC AsmParsers as guides. So far it is very simple and only supports sopp instructions. llvm-svn: 221994
-
- Oct 03, 2014
-
-
Adrian Prantl authored
llvm-svn: 219015
-
- Sep 26, 2014
-
-
Jyoti Allur authored
llvm-svn: 218504
-
- Aug 19, 2014
-
-
Alex Lorenz authored
Differential Revision: http://reviews.llvm.org/D4729 llvm-svn: 215990
-
- May 12, 2014
-
-
James Molloy authored
There are some interesting decisions based on non-obvious rationale in the ARM64-BE NEON implementation - decent documentation is definitely required. llvm-svn: 208577
-
- Apr 12, 2014
-
-
Duncan P. N. Exon Smith authored
Documents terminology used in the forthcoming rewrite of BlockFrequencyInfo. <rdar://problem/14292693> llvm-svn: 206086
-
- Apr 08, 2014
-
-
Sean Silva authored
docs/TableGen/ is not really just "fundamentals" anymore, but rather more of a portal for all things TableGen. llvm-svn: 205743
-
- Apr 01, 2014
-
-
Renato Golin authored
Making the new TableGen documentation official and marking the old file as "Moved". Also, reverting the original LangRef as the normative formal description of the language, while keeping the "new" LangRef as LangIntro for the less inlcined to reading language grammars. We should remove TableGenFundamentals.rst one day, but for now, just a warning that it moved will have to do, while we make sure there are no more links to it from elsewhere. llvm-svn: 205289
-
- Mar 20, 2014
-
-
Renato Golin authored
This is mainly a movement of content around to give place to new content allowing different people to add bits to it in the right place. There is some new content, but mostly to fill the gaps left by text movement. I'm dropping the old syntax documentation as it has the problem of being quickly outdated by changes and largely unnecessary to people not involved in creating the language, but using it, which is the whole point of the documentation. llvm-svn: 204351
-
- Mar 02, 2014
-
-
Sean Silva authored
The docs now build cleanly. Yay! The following warnings were fixed: /home/sean/pg/llvm/llvm/docs/HowToReleaseLLVM.rst:364: WARNING: Enumerated list ends without a blank line; unexpected unindent. /home/sean/pg/llvm/llvm/docs/InAlloca.rst:: WARNING: document isn't included in any toctree /home/sean/pg/llvm/llvm/docs/CodingStandards.rst:85: WARNING: Title underline too short. Supported C++11 Language and Library Features ------------------------------------------- /home/sean/pg/llvm/llvm/docs/CodingStandards.rst:85: WARNING: Title underline too short. Supported C++11 Language and Library Features ------------------------------------------- /home/sean/pg/llvm/llvm/docs/GettingStarted.rst:185: WARNING: Explicit markup ends without a blank line; unexpected unindent. /home/sean/pg/llvm/llvm/docs/GettingStarted.rst:565: WARNING: Explicit markup ends without a blank line; unexpected unindent. /home/sean/pg/llvm/llvm/docs/GettingStarted.rst:567: WARNING: Block quote ends without a blank line; unexpected unindent. llvm-svn: 202603
-
- Dec 24, 2013
-
-
Andrew Trick authored
These still have "experimental" status, meaning we don't guarantee backward compatibility. However, they are already actively used by the open source WebKit project, and have started to be adopted by other projects. llvm-svn: 197930
-
- Sep 09, 2013
-
-
Sean Silva authored
llvm-svn: 190326
-