summaryrefslogtreecommitdiffstats
path: root/llvm/docs/LangRef.html
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix an example in the documentation.Rafael Espindola2011-08-231-1/+1
| | | | | | Patch by Sanjoy Das! llvm-svn: 138346
* Some minor wording updates and cross-linking for atomic docs. Explicitly ↵Eli Friedman2011-08-221-11/+25
| | | | | | note that we don't try to portably define what volatile in LLVM IR means. llvm-svn: 138274
* Fixed some punctuation. Sentences can be combined with semi-colons but notJohn Criswell2011-08-191-2/+2
| | | | | | commas. llvm-svn: 138043
* Fix the getelementptr description so it is extremely clear that array ↵Eli Friedman2011-08-121-11/+13
| | | | | | indices passed to getelementptr are signed. llvm-svn: 137538
* Move "atomic" and "volatile" designations on instructions after the opcodeEli Friedman2011-08-121-6/+6
| | | | | | | | | | of the instruction. Note that this change affects the existing non-atomic load and store instructions; the parser now accepts both forms, and the change is noted in the release notes. llvm-svn: 137527
* Initial commit of the 'landingpad' instruction.Bill Wendling2011-08-121-6/+8
| | | | | | | | | | | | This implements the 'landingpad' instruction. It's used to indicate that a basic block is a landing pad. There are several restrictions on its use (see LangRef.html for more detail). These restrictions allow the exception handling code to gather the information it needs in a much more sane way. This patch has the definition, implementation, C interface, parsing, and bitcode support in it. llvm-svn: 137501
* fix one reference that slipped through, thanks EliChris Lattner2011-08-121-1/+1
| | | | llvm-svn: 137488
* add new accessors to reflect new terminology in struct types.Chris Lattner2011-08-121-10/+12
| | | | llvm-svn: 137468
* docs: Update HTML markup(s).NAKAMURA Takumi2011-08-121-12/+15
| | | | llvm-svn: 137433
* Fix minor typo.Eli Friedman2011-08-091-1/+1
| | | | llvm-svn: 137177
* Representation of 'atomic load' and 'atomic store' in IR.Eli Friedman2011-08-091-13/+34
| | | | llvm-svn: 137170
* Clean up the grammar for the landingpad instruction.Bill Wendling2011-08-081-2/+4
| | | | llvm-svn: 137042
* Fix typo found by John.Bill Wendling2011-08-081-1/+1
| | | | llvm-svn: 137040
* Go back to the old definition. It's not clear that a 'resume' can be ↵Bill Wendling2011-08-031-2/+2
| | | | | | 'outlined' from the function with the landing pad for all platforms. llvm-svn: 136799
* Explain how clauses are applied.Bill Wendling2011-08-031-0/+4
| | | | llvm-svn: 136790
* Add the documentation for the 'landingpad' instruction. Improve the 'invoke'Bill Wendling2011-08-021-4/+90
| | | | | | instruction's documentation to reference the landingpad and resume instructions. llvm-svn: 136729
* no need to count the terminators.Chris Lattner2011-08-021-9/+9
| | | | llvm-svn: 136718
* Minor wording tweak for memory model.Eli Friedman2011-08-021-4/+4
| | | | llvm-svn: 136668
* Fix some validation errors.Bill Wendling2011-07-311-0/+2
| | | | llvm-svn: 136591
* Fix some validation errors.Bill Wendling2011-07-311-3/+5
| | | | llvm-svn: 136590
* Add the 'resume' instruction for the new EH rewrite.Bill Wendling2011-07-311-2/+37
| | | | | | | | | This adds the 'resume' instruction class, IR parsing, and bitcode reading and writing. The 'resume' instruction resumes propagation of an existing (in-flight) exception whose unwinding was interrupted with a 'landingpad' instruction (to be added later). llvm-svn: 136589
* Revert r136253, r136263, r136269, r136313, r136325, r136326, r136329, r136338,Bill Wendling2011-07-301-33/+2
| | | | | | | r136339, r136341, r136369, r136387, r136392, r136396, r136429, r136430, r136444, r136445, r136446, r136253 pending review. llvm-svn: 136556
* LangRef and basic memory-representation/reading/writing for 'cmpxchg' andEli Friedman2011-07-281-8/+241
| | | | | | | | | | | | | | | | | | | | | 'atomicrmw' instructions, which allow representing all the current atomic rmw intrinsics. The allowed operands for these instructions are heavily restricted at the moment; we can probably loosen it a bit, but supporting general first-class types (where it makes sense) might get a bit complicated, given how SelectionDAG works. As an initial cut, these operations do not support specifying an alignment, but it would be possible to add if we think it's useful. Specifying an alignment lower than the natural alignment would be essentially impossible to support on anything other than x86, but specifying a greater alignment would be possible. I can't think of any useful optimizations which would use that information, but maybe someone else has ideas. Optimizer/codegen support coming soon. llvm-svn: 136404
* Merge the contents from exception-handling-rewrite to the mainline.Bill Wendling2011-07-271-2/+33
| | | | | | This adds the new instructions 'landingpad' and 'resume'. llvm-svn: 136253
* Fix a typo.Bill Wendling2011-07-261-1/+1
| | | | llvm-svn: 136133
* Clean up the HTML here a bit.Bill Wendling2011-07-261-1/+2
| | | | llvm-svn: 136074
* Initial implementation of 'fence' instruction, the new C++0x-style ↵Eli Friedman2011-07-251-0/+58
| | | | | | | | replacement for llvm.memory.barrier. This is just a LangRef entry and reading/writing/memory representation; optimizer+codegen support coming soon. llvm-svn: 136009
* Add uwtable to the langref.Rafael Espindola2011-07-251-0/+8
| | | | llvm-svn: 135913
* clarify that opaque is actually a struct type, PR10430Chris Lattner2011-07-231-5/+5
| | | | llvm-svn: 135861
* Some LangRef tweaks, per Dan's comments.Eli Friedman2011-07-221-13/+16
| | | | llvm-svn: 135744
* Commit LangRef changes for LLVM concurrency model. Start of supporting ↵Eli Friedman2011-07-201-0/+86
| | | | | | C++0x memory model and atomics. See thread on llvmdev titled "Reviving the new LLVM concurrency model". llvm-svn: 135624
* Land the long talked about "type system rewrite" patch. ThisChris Lattner2011-07-091-111/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | patch brings numerous advantages to LLVM. One way to look at it is through diffstat: 109 files changed, 3005 insertions(+), 5906 deletions(-) Removing almost 3K lines of code is a good thing. Other advantages include: 1. Value::getType() is a simple load that can be CSE'd, not a mutating union-find operation. 2. Types a uniqued and never move once created, defining away PATypeHolder. 3. Structs can be "named" now, and their name is part of the identity that uniques them. This means that the compiler doesn't merge them structurally which makes the IR much less confusing. 4. Now that there is no way to get a cycle in a type graph without a named struct type, "upreferences" go away. 5. Type refinement is completely gone, which should make LTO much MUCH faster in some common cases with C++ code. 6. Types are now generally immutable, so we can use "Type *" instead "const Type *" everywhere. Downsides of this patch are that it removes some functions from the C API, so people using those will have to upgrade to (not yet added) new API. "LLVM 3.0" is the right time to do this. There are still some cleanups pending after this, this patch is large enough as-is. llvm-svn: 134829
* Use add instead of accumulate.Cameron Zwarich2011-07-081-1/+1
| | | | llvm-svn: 134752
* Add an intrinsic and codegen support for fused multiply-accumulate. The intentCameron Zwarich2011-07-081-0/+32
| | | | | | is to use this for architectures that have a native FMA instruction. llvm-svn: 134742
* Generalize @llvm.ctlz, @llvm.cttz, and @llvm.ctpop to work on vectors of ↵Owen Anderson2011-07-011-9/+21
| | | | | | integers, and fix the one optimization pass that I'm aware of that needs updating for this. At least one current target, ARM NEON, can implement these operations on vectors directly. llvm-svn: 134265
* Add missing operand. rdar://9694169Evan Cheng2011-06-291-1/+1
| | | | llvm-svn: 134078
* Document nonlazybind.Dan Gohman2011-06-161-0/+5
| | | | llvm-svn: 133160
* Add one more argument to the prefetch intrinsic to indicate whether it's a dataBruno Cardoso Lopes2011-06-141-3/+5
| | | | | | | or instruction cache access. Update the targets to match it and also teach autoupgrade. llvm-svn: 132976
* Fix copy+pastos.Dan Gohman2011-05-271-2/+2
| | | | llvm-svn: 132168
* Document llvm.exp and llvm.pow. Dan Gohman2011-05-231-0/+68
| | | | llvm-svn: 131921
* insertvalue takes a variable number of arguments, document this, fixing PR9935.Chris Lattner2011-05-221-3/+4
| | | | llvm-svn: 131850
* Fix errors in this llvm ir example.Nick Lewycky2011-05-161-7/+7
| | | | llvm-svn: 131416
* docs: Introduce cascading style <div> and <p> continued on <h[2-5]>.NAKAMURA Takumi2011-04-231-234/+237
| | | | | | | | | | | | | | | | | <h2>Section Example</h2> <div> <!-- h2+div is applied --> <p>Section preamble.</p> <h3>Subsection Example</h3> <p> <!-- h3+p is applied --> Subsection body </p> <!-- End of section body --> </div> FIXME: Care H5 better. llvm-svn: 130040
* docs: Use <Hn> as Heading elements instead of <DIV class="doc_foo">.NAKAMURA Takumi2011-04-181-353/+484
| | | | | | | | | H1 ... doc_title H2 ... doc_section H3 ... doc_subsection H4 ... doc_subsubsection llvm-svn: 129736
* Fix a ton of comment typos found by codespell. Patch byChris Lattner2011-04-151-2/+2
| | | | | | Luis Felipe Strano Moraes! llvm-svn: 129558
* Fix a hole in the definition of "dependence" used by trap values. TrapDan Gohman2011-04-121-2/+22
| | | | | | | values are also transmitted through branches which cause side effects to be skipped altogether. llvm-svn: 129404
* docs: Canonicalize URLs.NAKAMURA Takumi2011-04-091-1/+1
| | | | llvm-svn: 129181
* Pick better examples. "fpext float 3.1415 to double" won't parse because 3.1415Nick Lewycky2011-03-311-2/+2
| | | | | | | isn't an exact float. Also "fpext float 1.0 to float" is invalid IR because it's not performing an extension. llvm-svn: 128647
* Change the signext language in LangRef to closer match zeroext.Cameron Zwarich2011-03-171-2/+3
| | | | llvm-svn: 127808
* The x86-64 ABI says that a bool is only guaranteed to be sign-extended to a byteCameron Zwarich2011-03-161-2/+3
| | | | | | | | | | | rather than an int. Thankfully, this only causes LLVM to miss optimizations, not generate incorrect code. This just fixes the zext at the return. We still insert an i32 ZextAssert when reading a function's arguments, but it is followed by a truncate and another i8 ZextAssert so it is not optimized. llvm-svn: 127766
OpenPOWER on IntegriCloud