From f5af6ada3b0570db1afc19029cad8fb8320676ef Mon Sep 17 00:00:00 2001 From: NAKAMURA Takumi Date: Sat, 23 Apr 2011 00:30:22 +0000 Subject: docs: Introduce cascading style
and

continued on .

Section Example

Section preamble.

Subsection Example

Subsection body

FIXME: Care H5 better. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@130040 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/LangRef.html | 471 +++++++++++++++++++++++++++--------------------------- 1 file changed, 237 insertions(+), 234 deletions(-) (limited to 'docs/LangRef.html') diff --git a/docs/LangRef.html b/docs/LangRef.html index 69e0a75..381fed5 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -324,7 +324,7 @@

Abstract

-
+

This document is a reference manual for the LLVM assembly language. LLVM is a Static Single Assignment (SSA) based representation that provides type @@ -338,7 +338,7 @@

Introduction

-
+

The LLVM code representation is designed to be used in three different forms: as an in-memory compiler IR, as an on-disk bitcode representation (suitable @@ -359,14 +359,12 @@ variable is never accessed outside of the current function, allowing it to be promoted to a simple SSA value instead of a memory location.

-
-

Well-Formedness

-
+

It is important to note that this document describes 'well formed' LLVM assembly language. There is a difference between what the parser accepts and @@ -386,13 +384,15 @@

+
+

Identifiers

-
+

LLVM identifiers come in two basic types: global and local. Global identifiers (functions, global variables) begin with the '@' @@ -479,13 +479,13 @@

High Level Structure

- +

Module Structure

-
+

LLVM programs are composed of "Module"s, each of which is a translation unit of the input programs. Each module consists of functions, global variables, @@ -535,7 +535,7 @@ define i32 @main() { ; i32()*   Linkage Types -

+

All Global Variables and Functions have one of the following types of linkage:

@@ -684,7 +684,7 @@ define i32 @main() { ; i32()*   Calling Conventions -
+

LLVM functions, calls and invokes can all have an optional calling @@ -757,7 +757,7 @@ define i32 @main() { ; i32()*   Visibility Styles -

+

All Global Variables and Functions have one of the following visibility styles:

@@ -791,7 +791,7 @@ define i32 @main() { ; i32()*   Named Types -
+

LLVM IR allows you to specify name aliases for certain types. This can make it easier to read the IR and make the IR more condensed (particularly when @@ -822,7 +822,7 @@ define i32 @main() { ; i32()*   Global Variables -

+

Global variables define regions of memory allocated at compilation time instead of run-time. Global variables may optionally be initialized, may @@ -890,7 +890,7 @@ define i32 @main() { ; i32()*   Functions -

+

LLVM function definitions consist of the "define" keyword, an optional linkage type, an optional @@ -953,7 +953,7 @@ define [linkage] [visibility] Aliases -

+

Aliases act as "second name" for the aliasee value (which can be either function, global variable, another alias or bitcast of global value). Aliases @@ -972,7 +972,7 @@ define [linkage] [visibility] Named Metadata -

+

Named metadata is a collection of metadata. Metadata nodes (but not metadata strings) are the only valid operands for @@ -995,7 +995,7 @@ define [linkage] [visibility] Parameter Attributes -

+

The return type and each parameter of a function type may have a set of parameter attributes associated with them. Parameter attributes are @@ -1106,7 +1106,7 @@ declare signext i8 @returns_signed_char() Garbage Collector Names -

+

Each function may specify a garbage collector name, which is simply a string:

@@ -1126,7 +1126,7 @@ define void @f() gc "name" { ... } Function Attributes -
+

Function attributes are set to communicate additional information about a function. Function attributes are considered to be part of the function, not @@ -1249,7 +1249,7 @@ define void @f() optsize { ... } Module-Level Inline Assembly -

+

Modules may contain "module-level inline asm" blocks, which corresponds to the GCC "file scope inline asm" blocks. These blocks are internally @@ -1275,7 +1275,7 @@ module asm "more can go here" Data Layout -

+

A module may specify a target specific data layout string that specifies how data is to be laid out in memory. The syntax for the data layout is @@ -1387,7 +1387,7 @@ target datalayout = "layout specification" Pointer Aliasing Rules -

+

Any memory access must be done through a pointer value associated with an address range of the memory access, otherwise the behavior @@ -1451,7 +1451,7 @@ to implement type-based alias analysis.

Volatile Memory Accesses -
+

Certain memory accesses, such as loads, stores, and

+
+

Type System

-
+

The LLVM type system is one of the most important features of the intermediate representation. Being typed enables a number of optimizations @@ -1478,14 +1480,12 @@ synchronization behavior.

and transformations that are not feasible to perform on normal three address code representations.

-
-

Type Classifications

-
+

The types fall into a few useful classifications:

@@ -1546,19 +1546,17 @@ synchronization behavior.

Primitive Types -
+

The primitive types are the fundamental building blocks of the LLVM system.

-
-

Integer Type

-
+
Overview:

The integer type is a very simple type that simply specifies an arbitrary @@ -1596,7 +1594,7 @@ synchronization behavior.

Floating Point Types -
+
@@ -1616,7 +1614,7 @@ synchronization behavior.

X86mmx Type -
+
Overview:

The x86mmx type represents a value held in an MMX register on an x86 machine. The operations allowed on it are quite limited: parameters and return values, load and store, and bitcast. User-specified MMX instructions are represented as intrinsic or asm calls with arguments and/or results of this type. There are no arrays, vectors or constants of this type.

@@ -1633,7 +1631,7 @@ synchronization behavior.

Void Type -
+
Overview:

The void type does not represent any value and has no size.

@@ -1650,7 +1648,7 @@ synchronization behavior.

Label Type -
+
Overview:

The label type represents code labels.

@@ -1667,7 +1665,7 @@ synchronization behavior.

Metadata Type -
+
Overview:

The metadata type represents embedded metadata. No derived types may be @@ -1681,13 +1679,14 @@ synchronization behavior.

+

Derived Types

-
+

The real power in LLVM comes from the derived types in the system. This is what allows a programmer to represent arrays, functions, pointers, and other @@ -1697,14 +1696,12 @@ synchronization behavior.

of another array.

-
-

Aggregate Types

-
+

Aggregate Types are a subset of derived types that can contain multiple member types. Arrays, @@ -1718,7 +1715,7 @@ synchronization behavior.

Array Type -
+
Overview:

The array type is a very simple derived type that arranges elements @@ -1778,7 +1775,7 @@ synchronization behavior.

Function Type -
+
Overview:

The function type can be thought of as a function signature. It consists of @@ -1833,7 +1830,7 @@ synchronization behavior.

Structure Type -
+
Overview:

The structure type is used to represent a collection of data members together @@ -1873,7 +1870,7 @@ synchronization behavior.

Packed Structure Type -
+
Overview:

The packed structure type is used to represent a collection of data members @@ -1912,7 +1909,7 @@ synchronization behavior.

Pointer Type -
+
Overview:

The pointer type is used to specify memory locations. @@ -1958,7 +1955,7 @@ synchronization behavior.

Vector Type -
+
Overview:

A vector type is a simple derived type that represents a vector of elements. @@ -1999,7 +1996,7 @@ synchronization behavior.

Opaque Type -
+
Overview:

Opaque types are used to represent unknown types in the system. This @@ -2022,12 +2019,14 @@ synchronization behavior.

+
+

Type Up-references

-
+
Overview:

An "up reference" allows you to refer to a lexically enclosing type without @@ -2070,23 +2069,23 @@ synchronization behavior.

+
+

Constants

-
+

LLVM has several different basic types of constants. This section describes them all and their syntax.

-
-

Simple Constants

-
+
Boolean constants
@@ -2144,7 +2143,7 @@ synchronization behavior.

Complex Constants -
+

Complex constants are a (potentially recursive) combination of simple constants and smaller complex constants.

@@ -2198,7 +2197,7 @@ synchronization behavior.

Global Variable and Function Addresses -
+

The addresses of global variables and functions are always implicitly valid @@ -2220,7 +2219,7 @@ synchronization behavior.

Undefined Values -
+

The string 'undef' can be used anywhere a constant is expected, and indicates that the user of the value may receive an unspecified bit-pattern. @@ -2363,7 +2362,7 @@ b: unreachable Trap Values -

+

Trap values are similar to undef values, however instead of representing an unspecified bit pattern, they represent the @@ -2491,7 +2490,7 @@ second_end: Addresses of Basic Blocks -

+

blockaddress(@function, %block)

@@ -2520,7 +2519,7 @@ second_end: Constant Expressions -
+

Constant expressions are used to allow expressions involving other constants to be used as constants. Constant expressions may be of @@ -2646,16 +2645,18 @@ second_end:

+
+

Other Values

- +

Inline Assembler Expressions

-
+

LLVM supports inline assembler expressions (as opposed to Module-Level Inline Assembly) through the use of @@ -2704,13 +2705,12 @@ call void asm alignstack "eieio", ""() documented here. Constraints on what can be done (e.g. duplication, moving, etc need to be documented). This is probably best done by reference to another document that covers inline asm from a holistic perspective.

-

Inline Asm Metadata

-
+

The call instructions that wrap inline asm nodes may have a "!srcloc" MDNode attached to it that contains a list of constant integers. If present, the @@ -2731,12 +2731,14 @@ call void asm sideeffect "something bad", ""(), !srcloc !42

+
+

Metadata Nodes and Metadata Strings

-
+

LLVM IR allows metadata to be attached to instructions in the program that can convey extra information about the code to the optimizers and code @@ -2778,13 +2780,14 @@ call void @llvm.dbg.value(metadata !24, i64 0, metadata !25)

+

Intrinsic Global Variables

- +

LLVM has a number of "magic" global variables that contain data that affect code generation or other IR semantics. These are documented here. All globals of this sort should have a section specified as "llvm.metadata". This @@ -2796,7 +2799,7 @@ by LLVM.

The 'llvm.used' Global Variable -
+

The @llvm.used global is an array with i8* element type which has appending linkage. This array contains a list of @@ -2833,7 +2836,7 @@ object file to prevent the assembler and linker from molesting the symbol.

-
+

The @llvm.compiler.used directive is the same as the @llvm.used directive, except that it only prevents the compiler from @@ -2851,7 +2854,7 @@ should not be exposed to source languages.

The 'llvm.global_ctors' Global Variable -
+
 %0 = type { i32, void ()* }
 @llvm.global_ctors = appending global [1 x %0] [%0 { i32 65535, void ()* @ctor }]
@@ -2866,7 +2869,7 @@ should not be exposed to source languages.

 The 'llvm.global_dtors' Global Variable
 
 
-

+

 
 %0 = type { i32, void ()* }
 @llvm.global_dtors = appending global [1 x %0] [%0 { i32 65535, void ()* @dtor }]
@@ -2877,12 +2880,13 @@ should not be exposed to source languages.

 
 

 
+

 
 
 
Instruction Reference

 
 
-

+

 
 
The LLVM instruction set consists of several different classifications of
    instructions: terminator
@@ -2891,14 +2895,12 @@ should not be exposed to source languages.

    memory instructions, and
    other instructions.

 
-

-
 
 

   Terminator Instructions
 

 
-

+

 
 
As mentioned previously, every basic block
    in a program ends with a "Terminator" instruction, which indicates which
@@ -2916,14 +2918,12 @@ should not be exposed to source languages.

    'unwind' instruction, and the
    'unreachable' instruction.

 
-

-
 
 

   'ret' Instruction
 

 
-

+

 
 
Syntax:

 
@@ -2973,7 +2973,7 @@ should not be exposed to source languages.

   'br' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3016,7 +3016,7 @@ IfUnequal:
    'switch' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3071,7 +3071,7 @@ IfUnequal:
    'indirectbr' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3119,7 +3119,7 @@ IfUnequal:
   'invoke' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3209,7 +3209,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'unwind' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3241,7 +3241,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'unreachable' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3259,12 +3259,14 @@ that the invoke/unwind semantics are likely to change in future versions.

 
 

 
+

+
 
 

   Binary Operations
 

 
-

+

 
 
Binary operators are used to do most of the computation in a program.  They
    require two operands of the same type, execute an operation on them, and
@@ -3274,14 +3276,12 @@ that the invoke/unwind semantics are likely to change in future versions.

 
 
There are several different binary operators:

 
-

-
 
 

   'add' Instruction
 

 
-

+

 
 
Syntax:

 
@@ -3326,7 +3326,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'fadd' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3356,7 +3356,7 @@ that the invoke/unwind semantics are likely to change in future versions.

    'sub' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3408,7 +3408,7 @@ that the invoke/unwind semantics are likely to change in future versions.

    'fsub' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3444,7 +3444,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'mul' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3494,7 +3494,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'fmul' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3524,7 +3524,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'udiv' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3565,7 +3565,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'sdiv' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3608,7 +3608,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'fdiv' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3638,7 +3638,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'urem' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3676,7 +3676,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'srem' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3727,7 +3727,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'frem' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3754,12 +3754,14 @@ that the invoke/unwind semantics are likely to change in future versions.

 
 

 
+

+
 
 

   Bitwise Binary Operations
 

 
-

+

 
 
Bitwise binary operators are used to do various forms of bit-twiddling in a
    program.  They are generally very efficient instructions and can commonly be
@@ -3767,14 +3769,12 @@ that the invoke/unwind semantics are likely to change in future versions.

    same type, execute an operation on them, and produce a single value.  The
    resulting value is the same type as its operands.

 
-

-
 
 

   'shl' Instruction
 

 
-

+

 
 
Syntax:

 
@@ -3825,7 +3825,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'lshr' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3872,7 +3872,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'ashr' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3919,7 +3919,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'and' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -3980,7 +3980,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'or' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4043,7 +4043,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'xor' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4103,12 +4103,14 @@ that the invoke/unwind semantics are likely to change in future versions.

 
 

 
+

+
 
 

   Vector Operations
 

 
-

+

 
 
LLVM supports several instructions to represent vector operations in a
    target-independent manner.  These instructions cover the element-access and
@@ -4117,14 +4119,12 @@ that the invoke/unwind semantics are likely to change in future versions.

    will want to use target-specific intrinsics to take full advantage of a
    specific target.

 
-

-
 
 

    'extractelement' Instruction
 

 
-

+

 
 
Syntax:

 
@@ -4160,7 +4160,7 @@ that the invoke/unwind semantics are likely to change in future versions.

    'insertelement' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4196,7 +4196,7 @@ that the invoke/unwind semantics are likely to change in future versions.

    'shufflevector' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4239,24 +4239,24 @@ that the invoke/unwind semantics are likely to change in future versions.

 
 

 
+

+
 
 

   Aggregate Operations
 

 
-

+

 
 
LLVM supports several instructions for working with
   aggregate values.

 
-

-
 
 

    'extractvalue' Instruction
 

 
-

+

 
 
Syntax:

 
@@ -4298,7 +4298,7 @@ that the invoke/unwind semantics are likely to change in future versions.

    'insertvalue' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4332,27 +4332,26 @@ that the invoke/unwind semantics are likely to change in future versions.

 
 

 
+

 
 
 

   Memory Access and Addressing Operations
 

 
-

+

 
 
A key design point of an SSA-based representation is how it represents
    memory.  In LLVM, no memory locations are in SSA form, which makes things
    very simple.  This section describes how to read, write, and allocate
    memory in LLVM.

 
-

-
 
 

   'alloca' Instruction
 

 
-

+

 
 
Syntax:

 
@@ -4403,7 +4402,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'load' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4462,7 +4461,7 @@ that the invoke/unwind semantics are likely to change in future versions.

   'store' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4524,7 +4523,7 @@ that the invoke/unwind semantics are likely to change in future versions.

    'getelementptr' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4650,25 +4649,25 @@ entry:
 
 

 
+

+
 
 

   Conversion Operations
 

 
-

+

 
 
The instructions in this category are the conversion instructions (casting)
    which all take a single operand and a type. They perform various bit
    conversions on the operand.

 
-

-
 
 

    'trunc .. to' Instruction
 

 
-

+

 
 
Syntax:

 
@@ -4708,7 +4707,7 @@ entry:
    'zext .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4748,7 +4747,7 @@ entry:
    'sext .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4787,7 +4786,7 @@ entry:
    'fptrunc .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4825,7 +4824,7 @@ entry:
    'fpext .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4862,7 +4861,7 @@ entry:
    'fptoui .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4900,7 +4899,7 @@ entry:
    'fptosi .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4939,7 +4938,7 @@ entry:
    'uitofp .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -4976,7 +4975,7 @@ entry:
    'sitofp .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5012,7 +5011,7 @@ entry:
    'ptrtoint .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5050,7 +5049,7 @@ entry:
    'inttoptr .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5088,7 +5087,7 @@ entry:
    'bitcast .. to' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5127,24 +5126,24 @@ entry:
 
 

 
+

+
 
 

   Other Operations
 

 
-

+

 
 
The instructions in this category are the "miscellaneous" instructions, which
    defy better classification.

 
-

-
 
 

   'icmp' Instruction
 

 
-

+

 
 
Syntax:

 
@@ -5247,7 +5246,7 @@ entry:
   'fcmp' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5368,7 +5367,7 @@ entry:
   'phi' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5416,7 +5415,7 @@ Loop:       ; Infinite loop that counts from 0 on up...
    'select' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5459,7 +5458,7 @@ Loop:       ; Infinite loop that counts from 0 on up...
   'call' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5568,7 +5567,7 @@ freestanding environments and non-C-based languages.

   'va_arg' Instruction
 
 
-

+

 
 
Syntax:

 
@@ -5609,11 +5608,15 @@ freestanding environments and non-C-based languages.

 
 

 
+

+
+

+
 
 
Intrinsic Functions

 
 
-

+

 
 
LLVM supports the notion of an "intrinsic function".  These functions have
    well known names and semantics and are required to follow certain
@@ -5656,14 +5659,12 @@ freestanding environments and non-C-based languages.

 
To learn how to add an intrinsic function, please see the
    Extending LLVM Guide.

 
-

-
 
 

   Variable Argument Handling Intrinsics
 

 
-

+

 
 
Variable argument support is defined in LLVM with
    the va_arg instruction and these three
@@ -5705,15 +5706,13 @@ declare void @llvm.va_copy(i8*, i8*)
 declare void @llvm.va_end(i8*)
 

 
-

-
 
 

   'llvm.va_start' Intrinsic
 

 
 
-

+

 
 
Syntax:

 
@@ -5743,7 +5742,7 @@ declare void @llvm.va_end(i8*)
  'llvm.va_end' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -5774,7 +5773,7 @@ declare void @llvm.va_end(i8*)
   'llvm.va_copy' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -5800,12 +5799,14 @@ declare void @llvm.va_end(i8*)
 
 

 
+

+
 
 

   Accurate Garbage Collection Intrinsics
 

 
-

+

 
 
LLVM support for Accurate Garbage
 Collection (GC) requires the implementation and generation of these
@@ -5820,14 +5821,12 @@ LLVM.

 
The garbage collection intrinsics only operate on objects in the generic
    address space (address space zero).

 
-

-
 
 

   'llvm.gcroot' Intrinsic
 

 
-

+

 
 
Syntax:

 
@@ -5858,7 +5857,7 @@ LLVM.

   'llvm.gcread' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -5890,7 +5889,7 @@ LLVM.

   'llvm.gcwrite' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -5917,24 +5916,24 @@ LLVM.

 
 

 
+

+
 
 

   Code Generator Intrinsics
 

 
-

+

 
 
These intrinsics are provided by LLVM to expose special features that may
    only be implemented with code generator support.

 
-

-
 
 

   'llvm.returnaddress' Intrinsic
 

 
-

+

 
 
Syntax:

 
@@ -5969,7 +5968,7 @@ LLVM.

   'llvm.frameaddress' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -6003,7 +6002,7 @@ LLVM.

   'llvm.stacksave' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -6033,7 +6032,7 @@ LLVM.

   'llvm.stackrestore' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -6058,7 +6057,7 @@ LLVM.

   'llvm.prefetch' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -6091,7 +6090,7 @@ LLVM.

   'llvm.pcmarker' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -6122,7 +6121,7 @@ LLVM.

   'llvm.readcyclecounter' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -6144,26 +6143,26 @@ LLVM.

 
 

 
+

+
 
 

   Standard C Library Intrinsics
 

 
-

+

 
 
LLVM provides intrinsics for a few important standard C library functions.
    These intrinsics allow source-language front-ends to pass information about
    the alignment of the pointer arguments to the code generator, providing
    opportunity for more efficient code generation.

 
-

-
 
 

   'llvm.memcpy' Intrinsic
 

 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.memcpy on any
@@ -6217,7 +6216,7 @@ LLVM.

   'llvm.memmove' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.memmove on any integer bit
@@ -6273,7 +6272,7 @@ LLVM.

   'llvm.memset.*' Intrinsics
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.memset on any integer bit
@@ -6323,7 +6322,7 @@ LLVM.

   'llvm.sqrt.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.sqrt on any
@@ -6361,7 +6360,7 @@ LLVM.

   'llvm.powi.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.powi on any
@@ -6397,7 +6396,7 @@ LLVM.

   'llvm.sin.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.sin on any
@@ -6431,7 +6430,7 @@ LLVM.

   'llvm.cos.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.cos on any
@@ -6465,7 +6464,7 @@ LLVM.

   'llvm.pow.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.pow on any
@@ -6495,24 +6494,24 @@ LLVM.

 
 

 
+

+
 
 

   Bit Manipulation Intrinsics
 

 
-

+

 
 
LLVM provides intrinsics for a few important bit manipulation operations.
    These allow efficient code generation for some algorithms.

 
-

-
 
 

   'llvm.bswap.*' Intrinsics
 

 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic function. You can use bswap on any integer
@@ -6547,7 +6546,7 @@ LLVM.

   'llvm.ctpop.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.ctpop on any integer bit
@@ -6579,7 +6578,7 @@ LLVM.

   'llvm.ctlz.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.ctlz on any
@@ -6613,7 +6612,7 @@ LLVM.

   'llvm.cttz.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.cttz on any
@@ -6642,17 +6641,17 @@ LLVM.

 
 

 
+

+
 
 

   Arithmetic with Overflow Intrinsics
 

 
-

+

 
 
LLVM provides intrinsics for some arithmetic with overflow operations.

 
-

-
 
 

   
@@ -6660,7 +6659,7 @@ LLVM.

   
 

 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.sadd.with.overflow
@@ -6708,7 +6707,7 @@ LLVM.

   
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.uadd.with.overflow
@@ -6755,7 +6754,7 @@ LLVM.

   
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.ssub.with.overflow
@@ -6803,7 +6802,7 @@ LLVM.

   
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.usub.with.overflow
@@ -6851,7 +6850,7 @@ LLVM.

   
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.smul.with.overflow
@@ -6900,7 +6899,7 @@ LLVM.

   
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.umul.with.overflow
@@ -6941,12 +6940,14 @@ LLVM.

 
 

 
+

+
 
 

   Half Precision Floating Point Intrinsics
 

 
-

+

 
 
Half precision floating point is a storage-only format. This means that it is
    a dense encoding (in memory) but does not support computation in the
@@ -6960,7 +6961,6 @@ LLVM.

    float if needed, then converted to i16 with
    llvm.convert.to.fp16, then
    storing as an i16 value.

-

 
 
 

@@ -6969,7 +6969,7 @@ LLVM.

   
 

 
-

+

 
 
Syntax:

 
@@ -7006,7 +7006,7 @@ LLVM.

   
 
 
-

+

 
 
Syntax:

 
@@ -7036,12 +7036,14 @@ LLVM.

 
 

 
+

+
 
 

   Debugger Intrinsics
 

 
-

+

 
 
The LLVM debugger intrinsics (which all start with llvm.dbg.
    prefix), are described in
@@ -7055,7 +7057,7 @@ LLVM.

   Exception Handling Intrinsics
 
 
-

+

 
 
The LLVM exception handling intrinsics (which all start with
    llvm.eh. prefix), are described in
@@ -7069,7 +7071,7 @@ LLVM.

   Trampoline Intrinsic
 
 
-

+

 
 
This intrinsic makes it possible to excise one parameter, marked with
    the nest attribute, from a function.
@@ -7095,8 +7097,6 @@ LLVM.

 
The call %val = call i32 %fp(i32 %x, i32 %y) is then equivalent
    to %val = call i32 %f(i8* %nval, i32 %x, i32 %y).

 
-

-
 
 

   
@@ -7104,7 +7104,7 @@ LLVM.

   
 

 
-

+

 
 
Syntax:

 
@@ -7141,12 +7141,14 @@ LLVM.

 
 

 
+

+
 
 

   Atomic Operations and Synchronization Intrinsics
 

 
-

+

 
 
These intrinsic functions expand the "universal IR" of LLVM to represent
    hardware constructs for atomic operations and memory synchronization.  This
@@ -7166,14 +7168,12 @@ LLVM.

    No one model or paradigm should be selected above others unless the hardware
    itself ubiquitously does so.

 
-

-
 
 

   'llvm.memory.barrier' Intrinsic
 

 
-

+

 
Syntax:

 
   declare void @llvm.memory.barrier(i1 <ll>, i1 <ls>, i1 <sl>, i1 <ss>, i1 <device>)
@@ -7245,7 +7245,7 @@ LLVM.

   'llvm.atomic.cmp.swap.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.atomic.cmp.swap on
@@ -7305,7 +7305,7 @@ LLVM.

   'llvm.atomic.swap.*' Intrinsic
 
 
-

+

 
Syntax:

 
 
This is an overloaded intrinsic. You can use llvm.atomic.swap on any
@@ -7362,7 +7362,7 @@ LLVM.

   'llvm.atomic.load.add.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.atomic.load.add on
@@ -7411,7 +7411,7 @@ LLVM.

   'llvm.atomic.load.sub.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use llvm.atomic.load.sub on
@@ -7476,7 +7476,7 @@ LLVM.

   
 
 
-

+

 
 
Syntax:

 
These are overloaded intrinsics. You can
@@ -7567,7 +7567,7 @@ LLVM.

   
 
 
-

+

 
 
Syntax:

 
These are overloaded intrinsics. You can use llvm.atomic.load_max,
@@ -7638,25 +7638,24 @@ LLVM.

 
 

 
+

 
 
 

   Memory Use Markers
 

 
-

+

 
 
This class of intrinsics exists to information about the lifetime of memory
    objects and ranges where variables are immutable.

 
-

-
 
 

   'llvm.lifetime.start' Intrinsic
 

 
-

+

 
 
Syntax:

 
@@ -7686,7 +7685,7 @@ LLVM.

   'llvm.lifetime.end' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -7715,7 +7714,7 @@ LLVM.

   'llvm.invariant.start' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -7743,7 +7742,7 @@ LLVM.

   'llvm.invariant.end' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -7765,24 +7764,24 @@ LLVM.

 
 

 
+

+
 
 

   General Intrinsics
 

 
-

+

 
 
This class of intrinsics is designed to be generic and has no specific
    purpose.

 
-

-
 
 

   'llvm.var.annotation' Intrinsic
 

 
-

+

 
 
Syntax:

 
@@ -7810,7 +7809,7 @@ LLVM.

   'llvm.annotation.*' Intrinsic
 
 
-

+

 
 
Syntax:

 
This is an overloaded intrinsic. You can use 'llvm.annotation' on
@@ -7846,7 +7845,7 @@ LLVM.

   'llvm.trap' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -7871,7 +7870,7 @@ LLVM.

   'llvm.stackprotector' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -7905,7 +7904,7 @@ LLVM.

   'llvm.objectsize' Intrinsic
 
 
-

+

 
 
Syntax:

 
@@ -7935,6 +7934,10 @@ LLVM.

 
 

 
+

+
+

+
 
 

 

-- 
cgit v1.1