summaryrefslogtreecommitdiffstats
path: root/llvm/docs
Commit message (Collapse)AuthorAgeFilesLines
...
* DI: Line up comments in examplesDuncan P. N. Exon Smith2014-10-041-27/+27
| | | | llvm-svn: 219055
* DI: Fixup example IR from r219051Duncan P. N. Exon Smith2014-10-041-3/+4
| | | | llvm-svn: 219054
* DI: Prune another exampleDuncan P. N. Exon Smith2014-10-041-62/+0
| | | | llvm-svn: 219053
* DI: Update and prune metadata examplesDuncan P. N. Exon Smith2014-10-041-502/+86
| | | | | | | Update a couple of the examples of debug info metadata, and prune the rest. Point to the true reference implementation in the source. llvm-svn: 219051
* Fix typo in TableGen documentationJonathan Roelofs2014-10-031-1/+1
| | | | llvm-svn: 219018
* Add a reference to Phabricator.rst to docs/index.rst.Adrian Prantl2014-10-031-0/+5
| | | | llvm-svn: 219015
* Revert "Revert "DI: Fold constant arguments into a single MDString""Duncan P. N. Exon Smith2014-10-031-90/+111
| | | | | | | | | | | | | | | | | | | | | | This reverts commit r218918, effectively reapplying r218914 after fixing an Ocaml bindings test and an Asan crash. The root cause of the latter was a tightened-up check in `DILexicalBlock::Verify()`, so I'll file a PR to investigate who requires the loose check (and why). Original commit message follows. -- This patch addresses the first stage of PR17891 by folding constant arguments together into a single MDString. Integers are stringified and a `\0` character is used as a separator. Part of PR17891. Note: I've attached my testcases upgrade scripts to the PR. If I've just broken your out-of-tree testcases, they might help. llvm-svn: 219010
* [sphinx cleanup] Fix unexpected indentation warning introduced by r218937Dan Liew2014-10-031-0/+2
| | | | llvm-svn: 218982
* Update Atomics.rstRobin Morisset2014-10-031-16/+36
| | | | | | | | | | | | | | | | Summary: I changed various bits of the compilation of atomics recently, and forgot updating the documentation. This patch just brings it up to date. Test Plan: no change to the code Reviewers: jfb Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D5590 llvm-svn: 218937
* Revert "DI: Fold constant arguments into a single MDString"Duncan P. N. Exon Smith2014-10-021-111/+90
| | | | | | This reverts commit r218914 while I investigate some bots. llvm-svn: 218918
* DI: Fold constant arguments into a single MDStringDuncan P. N. Exon Smith2014-10-021-90/+111
| | | | | | | | | | | | | This patch addresses the first stage of PR17891 by folding constant arguments together into a single MDString. Integers are stringified and a `\0` character is used as a separator. Part of PR17891. Note: I've attached my testcases upgrade scripts to the PR. If I've just broken your out-of-tree testcases, they might help. llvm-svn: 218914
* Move the complex address expression out of DIVariable and into an extraAdrian Prantl2014-10-011-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | argument of the llvm.dbg.declare/llvm.dbg.value intrinsics. Previously, DIVariable was a variable-length field that has an optional reference to a Metadata array consisting of a variable number of complex address expressions. In the case of OpPiece expressions this is wasting a lot of storage in IR, because when an aggregate type is, e.g., SROA'd into all of its n individual members, the IR will contain n copies of the DIVariable, all alike, only differing in the complex address reference at the end. By making the complex address into an extra argument of the dbg.value/dbg.declare intrinsics, all of the pieces can reference the same variable and the complex address expressions can be uniqued across the CU, too. Down the road, this will allow us to move other flags, such as "indirection" out of the DIVariable, too. The new intrinsics look like this: declare void @llvm.dbg.declare(metadata %storage, metadata %var, metadata %expr) declare void @llvm.dbg.value(metadata %storage, i64 %offset, metadata %var, metadata %expr) This patch adds a new LLVM-local tag to DIExpressions, so we can detect and pretty-print DIExpression metadata nodes. What this patch doesn't do: This patch does not touch the "Indirect" field in DIVariable; but moving that into the expression would be a natural next step. http://reviews.llvm.org/D4919 rdar://problem/17994491 Thanks to dblaikie and dexonsmith for reviewing this patch! Note: I accidentally committed a bogus older version of this patch previously. llvm-svn: 218787
* Revert r218778 while investigating buldbot breakage.Adrian Prantl2014-10-011-15/+2
| | | | | | "Move the complex address expression out of DIVariable and into an extra" llvm-svn: 218782
* Move the complex address expression out of DIVariable and into an extraAdrian Prantl2014-10-011-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | argument of the llvm.dbg.declare/llvm.dbg.value intrinsics. Previously, DIVariable was a variable-length field that has an optional reference to a Metadata array consisting of a variable number of complex address expressions. In the case of OpPiece expressions this is wasting a lot of storage in IR, because when an aggregate type is, e.g., SROA'd into all of its n individual members, the IR will contain n copies of the DIVariable, all alike, only differing in the complex address reference at the end. By making the complex address into an extra argument of the dbg.value/dbg.declare intrinsics, all of the pieces can reference the same variable and the complex address expressions can be uniqued across the CU, too. Down the road, this will allow us to move other flags, such as "indirection" out of the DIVariable, too. The new intrinsics look like this: declare void @llvm.dbg.declare(metadata %storage, metadata %var, metadata %expr) declare void @llvm.dbg.value(metadata %storage, i64 %offset, metadata %var, metadata %expr) This patch adds a new LLVM-local tag to DIExpressions, so we can detect and pretty-print DIExpression metadata nodes. What this patch doesn't do: This patch does not touch the "Indirect" field in DIVariable; but moving that into the expression would be a natural next step. http://reviews.llvm.org/D4919 rdar://problem/17994491 Thanks to dblaikie and dexonsmith for reviewing this patch! llvm-svn: 218778
* fix a typo in doumentation index.Jyoti Allur2014-09-261-1/+1
| | | | llvm-svn: 218504
* Update my previous commit to fit 80 cols...Sylvestre Ledru2014-09-251-1/+2
| | | | llvm-svn: 218448
* Details that -debug-only is not available when LLVM is built with ↵Sylvestre Ledru2014-09-251-0/+2
| | | | | | --enable-optimized llvm-svn: 218447
* [docs] Fixed a typo in Atomics.rstJingyue Wu2014-09-231-4/+4
| | | | llvm-svn: 218319
* Fix sphinx warning.Peter Collingbourne2014-09-181-3/+5
| | | | llvm-svn: 218081
* LTO: introduce object file-based on-disk module format.Peter Collingbourne2014-09-182-2/+19
| | | | | | | | | | | | | | | | | | This format is simply a regular object file with the bitcode stored in a section named ".llvmbc", plus any number of other (non-allocated) sections. One immediate use case for this is to accommodate compilation processes which expect the object file to contain metadata in non-allocated sections, such as the ".go_export" section used by some Go compilers [1], although I imagine that in the future we could consider compiling parts of the module (such as large non-inlinable functions) directly into the object file to improve LTO efficiency. [1] http://golang.org/doc/install/gccgo#Imports Differential Revision: http://reviews.llvm.org/D4371 llvm-svn: 218078
* [docs] Mention character array constants in docs/LangRef.rstDaniel Sanders2014-09-111-1/+3
| | | | | | | | | | | | | | | | | | Summary: They were used in the 'Module Structure' example but weren't otherwise documented. Credit to Reed Kotler for noticing. Reviewers: hans Reviewed By: hans Subscribers: hans, llvm-commits Differential Revision: http://reviews.llvm.org/D5191 llvm-svn: 217583
* [sphinx cleanup]Dan Liew2014-09-101-1/+1
| | | | | | Fix sphinx warning introduced by r217537 llvm-svn: 217541
* Fix docs reference to inexistent class.Nico Weber2014-09-101-2/+2
| | | | | | Patch sent via telegraph by TNorthover. Thanks! llvm-svn: 217537
* LangRef: @baz should be @bar in the COMDAT exampleHans Wennborg2014-09-101-1/+1
| | | | llvm-svn: 217520
* Fix type error in insertvalue example in LangRef. %agg1 is of type {i32,Dan Liew2014-09-081-1/+1
| | | | | | float} and thus cannot be used where a type {i32, {float}} is expected. llvm-svn: 217405
* [docs] Document what "NFC" means in a commit message.Sean Silva2014-09-061-0/+9
| | | | llvm-svn: 217292
* Minor typo.Andrew Trick2014-09-051-1/+1
| | | | llvm-svn: 217226
* Fix link to 3.5 release notes.Nico Weber2014-09-041-1/+1
| | | | llvm-svn: 217164
* Document !and. Fix !shl and friends -- they provide binary operations.Joerg Sonnenberger2014-09-032-3/+3
| | | | llvm-svn: 217034
* Reinstate "Nuke the old JIT."Eric Christopher2014-09-021-2/+1
| | | | | | | | Approved by Jim Grosbach, Lang Hames, Rafael Espindola. This reinstates commits r215111, 215115, 215116, 215117, 215136. llvm-svn: 216982
* Add a note about AuroraUX to the release notes.Rafael Espindola2014-09-021-0/+2
| | | | llvm-svn: 216938
* Add note to documentation about machine node chains.Matt Arsenault2014-09-021-1/+3
| | | | | | | | | | I've been assuming chain operands were always the first operand, since the documentation says this. I was confused about why they were missing after instruction selection. Apparently the convention changes to using the last operand for MachineSDNodes and I've never noticed before. llvm-svn: 216934
* Fix typos in comments, NFCRobin Morisset2014-08-291-1/+1
| | | | | | | | | | | | | | Summary: Just fixing comments, no functional change. Test Plan: N/A Reviewers: jfb Subscribers: mcrosier, llvm-commits Differential Revision: http://reviews.llvm.org/D5130 llvm-svn: 216784
* Introduce -DLLVM_USE_SANITIZER=Undefined CMake option to build UBSan-ified ↵Alexey Samsonov2014-08-291-2/+2
| | | | | | | | | version of LLVM/Clang. I've fixed most of the simple bugs and currently "check-llvm" test suite has 26 failures, and "check-clang" suite has 5 failures. llvm-svn: 216701
* Declare that musttail calls in variadic functions forward the ellipsisReid Kleckner2014-08-261-0/+3
| | | | | | | | | | | | | | | | | Summary: There is no functionality change here except in the way we assemble and dump musttail calls in variadic functions. There's really no need to separate out the bits for musttail and "is forwarding varargs" on call instructions. A musttail call by definition has to forward the ellipsis or it would fail verification. Reviewers: chandlerc, nlewycky Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D4892 llvm-svn: 216423
* ProgrammersManual: the flag is called -debug-onlyHans Wennborg2014-08-231-1/+1
| | | | llvm-svn: 216316
* Clear the llvm release notes to make room for 3.6.Rafael Espindola2014-08-221-153/+11
| | | | llvm-svn: 216292
* Use DILexicalBlockFile, rather than DILexicalBlock, to track discriminator ↵David Blaikie2014-08-211-5/+3
| | | | | | | | | | | | | | | changes to ensure discriminator changes don't introduce new DWARF DW_TAG_lexical_blocks. Somewhat unnoticed in the original implementation of discriminators, but it could cause instructions to end up in new, small, DW_TAG_lexical_blocks due to the use of DILexicalBlock to track discriminator changes. Instead, use DILexicalBlockFile which we already use to track file changes without introducing new scopes, so it works well to track discriminator changes in the same way. llvm-svn: 216239
* [LIT] Remove documentation for method since it does not existEric Fiselier2014-08-211-8/+0
| | | | llvm-svn: 216204
* Add note to LangRef about how function arguments can be unnamed andDan Liew2014-08-201-3/+12
| | | | | | how this affects the numbering of unnamed temporaries. llvm-svn: 216070
* LangRef: Move example of function-scope uselistorder to a functionDuncan P. N. Exon Smith2014-08-191-3/+10
| | | | | | Should make the example added in r216025 a little more clear. llvm-svn: 216027
* IR: Implement uselistorder assembly directivesDuncan P. N. Exon Smith2014-08-191-0/+39
| | | | | | | | | | Implement `uselistorder` and `uselistorder_bb` assembly directives, which allow the use-list order to be recovered when round-tripping to assembly. This is the bulk of PR20515. llvm-svn: 216025
* Docs: add documentation for the coverage mapping format.Alex Lorenz2014-08-192-0/+579
| | | | | | Differential Revision: http://reviews.llvm.org/D4729 llvm-svn: 215990
* CodingStandards: Document std::equal misbehaviourDuncan P. N. Exon Smith2014-08-191-0/+2
| | | | | | | I should have included this as part of r215986, which worked around this corner by changing ArrayRef::equals() not to use std::equal. Alas. llvm-svn: 215988
* [LIT]Correct name of global lit configuration object to be lit_config (not lit).Eric Fiselier2014-08-151-1/+1
| | | | llvm-svn: 215695
* Delete support for AuroraUX.Rafael Espindola2014-08-141-1/+0
| | | | | | | | | auroraux.org is not resolving. I will add this to the release notes as soon as I figure out where to put the 3.6 release notes :-) llvm-svn: 215645
* Add SPHINX_WARNINGS_AS_ERRORS CMake option to allow warnings to not beDan Liew2014-08-141-0/+4
| | | | | | | treated as errors (which is still the default). This is useful when working on documentation that has existing errors. llvm-svn: 215634
* Fix examples of "named metadata" (some of which isn't named).Nick Lewycky2014-08-131-2/+2
| | | | llvm-svn: 215522
* Fix typos:Sylvestre Ledru2014-08-111-1/+1
| | | | | | | * libaries => libraries * avaiable => available llvm-svn: 215366
* Temporarily Revert "Nuke the old JIT." as it's not quite ready toEric Christopher2014-08-071-1/+2
| | | | | | | | | | | be deleted. This will be reapplied as soon as possible and before the 3.6 branch date at any rate. Approved by Jim Grosbach, Lang Hames, Rafael Espindola. This reverts commits r215111, 215115, 215116, 215117, 215136. llvm-svn: 215154
OpenPOWER on IntegriCloud