A comment in a static section.

A static variant of a literal value.

For uninitialised data.

Defines a static LMString.

A static array.

A static structure type.

A pointer to other data.

Pointer to Pointer conversion.

Pointer to Integer conversion.

Constant addition operation.

Constant subtraction operation.

Fixed amount of arguments.

Variable amount of arguments.

Let the LLVM decide what section to put this in.

Put it in this specific section.

Comment meta-instruction.

Set meta instruction v1 = value. This isn't accepted by the real LLVM compiler. ISet instructions are erased by the Clean transform.

No operation. This isn't accepted by the real LLVM compiler. INop instructions are erased by the Clean transform.

Return a result.

Unconditional branch to the target label.

Conditional branch.

Mutliway branch. If scruitniee matches one of the literals in the list then jump to the corresponding label, otherwise jump to the default.

Informs the optimizer that instructions after this point are unreachable.

Cast the variable from to the to type. This is an abstraction of three cast operators in Llvm, inttoptr, prttoint and bitcast.

Load a value from memory.

Store a value to memory. First expression gives the destination pointer.

Integer comparison.

Floating-point comparison.

Call a function. Only NoReturn, NoUnwind and ReadNone attributes are valid.

Void type

An integer with a given width in bits.

32-bit floating point

64-bit floating point

80 bit (x86 only) floating point

128 bit floating point

A block label.

A pointer to another type of thing.

An array of things.

A structure type.

A type alias.

Function type, used to create pointers to functions.

Use of a variable.

A literal.

An undefined value.

An integer literal

A floating-point literal.

A null pointer literal. Only applicable to pointer types

A completely undefined value.

add two integers, floating point or vector values.

subtract two ...

multiply ..

unsigned integer or vector division.

signed integer ..

unsigned integer or vector remainder

signed ...

add two floating point or vector values.

subtract two ...

multiply ...

divide ...

remainder ...

Left shift.

Logical shift right

Arithmetic shift right. The most significant bits of the result will be equal to the sign bit of the left operand.

AND bitwise logical operation.

OR bitwise logical operation.

XOR bitwise logical operation.

Equal (Signed and Unsigned)

Not equal (Signed and Unsigned)

Unsigned greater than

Unsigned greater than or equal

Unsigned less than

Unsigned less than or equal

Signed greater than

Signed greater than or equal

Signed less than

Signed less than or equal

Always yields false, regardless of operands.

Both operands are not a QNAN and op1 is equal to op2.

Both operands are not a QNAN and op1 is greater than op2.

Both operands are not a QNAN and op1 is greater than or equal to op2.

Both operands are not a QNAN and op1 is less than op2.

Both operands are not a QNAN and op1 is less than or equal to op2.

Both operands are not a QNAN and op1 is not equal to op2.

Both operands are not a QNAN.

Either operand is a QNAN or op1 is equal to op2.

Either operand is a QNAN or op1 is greater than op2.

Either operand is a QNAN or op1 is greater than or equal to op2.

Either operand is a QNAN or op1 is less than op2.

Either operand is a QNAN or op1 is less than or equal to op2.

Either operand is a QNAN or op1 is not equal to op2.

Either operand is a QNAN.

Always yields true, regardless of operands.

Integer truncate

Integer extend (zero fill)

Integer extend (sign fill)

Float truncate

Float extend

Float to unsigned Integer

Float to signed Integer

Unsigned Integer to Float

Signed Int to Float

Pointer to Integer

Integer to Pointer

Cast between types where no bit manipulation is needed

The inliner should attempt to inline this function into callers whenever possible, ignoring any active inlining size threshold for this caller.

The source code contained a hint that inlining this function is desirable (such as the "inline" keyword in C/C++). It is just a hint; it imposes no requirements on the inliner.

The inliner should never inline this function in any situation. This attribute may not be used together with the alwaysinline attribute.

Suggests that optimization passes and code generator passes make choices that keep the code size of this function low, and otherwise do optimizations specifically to reduce code size.

The function never returns normally. This produces undefined behavior at runtime if the function ever does dynamically return.

The function never returns with an unwind or exceptional control flow. If the function does unwind, its runtime behavior is undefined.

The function computes its result (or decides to unwind an exception) based strictly on its arguments, without dereferencing any pointer arguments or otherwise accessing any mutable state (e.g. memory, control registers, etc) visible to caller functions. It does not write through any pointer arguments (including byval arguments) and never changes any state visible to callers. This means that it cannot unwind exceptions by calling the C++ exception throwing methods, but could use the unwind instruction.

The function does not write through any pointer arguments (including byval arguments) or otherwise modify any state (e.g. memory, control registers, etc) visible to caller functions. It may dereference pointer arguments and read state that may be set in the caller. A readonly function always returns the same value (or unwinds an exception identically) when called with the same set of arguments and global state. It cannot unwind an exception by calling the C++ exception throwing methods, but may use the unwind instruction.

The function should emit a stack smashing protector. It is in the form of a "canary"—a random value placed on the stack before the local variables that's checked upon return from the function to see if it has been overwritten. A heuristic is used to determine if a function needs stack protectors or not. If a function that has an ssp attribute is inlined into a function that doesn't have an ssp attribute, then the resulting function will have an ssp attribute.

The function should always emit a stack smashing protector. This overrides the ssp function attribute. If a function that has an sspreq attribute is inlined into a function that doesn't have an sspreq attribute or which has an ssp attribute, then the resulting function will have an sspreq attribute.

The code generator should not use a red zone, even if the target-specific ABI normally permits it.

Disables implicit floating point instructions.

Disables prologue / epilogue emission for the function. This can have very system-specific consequences.

That the parameter or return value should be zero-extended to a 32-bit value by the caller (for a parameter) or the callee (for a return value).

The parameter or return value should be sign-extended to a 32-bit value by the caller (for a parameter) or the callee (for a return value).

The parameter or return value should be treated in a special target-dependent fashion during while emitting code for a function call or return (usually, by putting it in a register as opposed to memory).

The pointer parameter should really be passed by value to the function.

The pointer parameter specifies the address of a structure that is the return value of the function in the source program.

The pointer does not alias any global or any other parameter.

The callee does not make any copies of the pointer that outlive the callee itself.

The pointer parameter can be excised using the trampoline intrinsics.

The C calling convention. This calling convention (the default if no other calling convention is specified) matches the target C calling conventions. This calling convention supports varargs function calls and tolerates some mismatch in the declared prototype and implemented declaration of the function (as does normal C).

This calling convention attempts to make calls as fast as possible (e.g. by passing things in registers). This calling convention allows the target to use whatever tricks it wants to produce fast code for the target, without having to conform to an externally specified ABI (Application Binary Interface). Implementations of this convention should allow arbitrary tail call optimization to be supported. This calling convention does not support varargs and requires the prototype of al callees to exactly match the prototype of the function definition.

This calling convention attempts to make code in the caller as efficient as possible under the assumption that the call is not commonly executed. As such, these calls often preserve all registers so that the call does not break any live ranges in the caller side. This calling convention does not support varargs and requires the prototype of all callees to exactly match the prototype of the function definition.

Any calling convention may be specified by number, allowing target-specific calling conventions to be used. Target specific calling conventions start at 64.

X86 Specific StdCall convention. LLVM includes a specific alias for it rather than just using CC_Ncc.

Normal call, allocate a new stack frame.

Tail call, perform the call in the current stack frame.

Global values with internal linkage are only directly accessible by objects in the current module. In particular, linking code into a module with an internal global value may cause the internal to be renamed as necessary to avoid collisions. Because the symbol is internal to the module, all references can be updated. This corresponds to the notion of the static keyword in C.

Globals with linkonce linkage are merged with other globals of the same name when linkage occurs. This is typically used to implement inline functions, templates, or other code which must be generated in each translation unit that uses it. Unreferenced linkonce globals are allowed to be discarded.

weak linkage is exactly the same as linkonce linkage, except that unreferenced weak globals may not be discarded. This is used for globals that may be emitted in multiple translation units, but that are not guaranteed to be emitted into every translation unit that uses them. One example of this are common globals in C, such as int X; at global scope.

appending linkage may only be applied to global variables of pointer to array type. When two global variables with appending linkage are linked together, the two global arrays are appended together. This is the Llvm, typesafe, equivalent of having the system linker append together sections with identical names when .o files are linked.

The semantics of this linkage follow the ELF model: the symbol is weak until linked, if not linked, the symbol becomes null instead of being an undefined reference.

The symbol participates in linkage and can be used to resolve external symbol references.

Alias for ExternallyVisible but with explicit textual form in LLVM assembly.