The LLVM code representation is designed to be used in three -different forms: as an in-memory compiler IR, as an on-disk bytecode +different forms: as an in-memory compiler IR, as an on-disk bitcode representation (suitable for fast loading by a Just-In-Time compiler), and as a human readable assembly language representation. This allows LLVM to provide a powerful intermediate representation for efficient @@ -262,12 +282,12 @@ following instruction is syntactically okay, but not well formed:
its uses. The LLVM infrastructure provides a verification pass that may be used to verify that an LLVM module is well formed. This pass is automatically run by the parser after parsing input assembly and by -the optimizer before it outputs bytecode. The violations pointed out +the optimizer before it outputs bitcode. The violations pointed out by the verifier pass indicate bugs in transformation passes or input to the parser.LLVM uses three different forms of identifiers, for different -purposes:
+LLVM identifiers come in two basic types: global and local. Global + identifiers (functions, global variables) begin with the @ character. Local + identifiers (register names, types) begin with the % character. Additionally, + there are three different formats for identifiers, for different purposes:
LLVM requires that values start with a '%' sign for two reasons: Compilers +
LLVM requires that values start with a prefix for two reasons: Compilers don't need to worry about name clashes with reserved words, and the set of reserved words may be expanded in the future without penalty. Additionally, unnamed identifiers allow a compiler to quickly come up with a temporary @@ -306,7 +328,7 @@ languages. There are keywords for different opcodes 'ret', etc...), for primitive type names ('void', 'i32', etc...), and others. These reserved words cannot conflict with variable names, because -none of them start with a '%' character.
+none of them start with a prefix character ('%' or '@').Here is an example of LLVM code to multiply the integer variable '%X' by 8:
@@ -388,7 +410,7 @@ symbol table entries. Here is an example of the "hello world" module: define i32 @main() { ; i32()* ; Convert [13x i8 ]* to i8 *... %cast210 = getelementptr [13 x i8 ]* %.LC0, i64 0, i64 0 ; i8 * + href="#i_getelementptr">getelementptr [13 x i8 ]* @.LC0, i64 0, i64 0 ; i8 * ; Call puts function to write out the string to stdout... +A global variable may be declared to reside in a target-specifc numbered +address space. For targets that support them, address spaces may affect how +optimizations are performed and/or what target instructions are used to access +the variable. The default address space is zero. The address space qualifier +must precede any other attributes.
+LLVM allows an explicit section to be specified for globals. If the target supports it, it will emit globals to the section specified.
@@ -656,12 +684,12 @@ to whatever it feels convenient. If an explicit alignment is specified, the global is forced to have at least that much alignment. All alignments must be a power of 2. -For example, the following defines a global with an initializer, section, - and alignment:
+For example, the following defines a global in a numbered address space with +an initializer, section, and alignment:
-%G = constant float 1.0, section "foo", align 4 +@G = constant float 1.0 addrspace(5), section "foo", align 4
A function definition contains a list of basic blocks, forming the CFG for the function. Each basic block may optionally start with a label (giving the @@ -704,11 +733,6 @@ basic blocks (i.e. there can not be any branches to the entry block of a function). Because the block can have no predecessors, it also cannot have any PHI nodes.
-LLVM functions are identified by their name and type signature. Hence, two -functions with the same name but different parameter lists or return values are -considered different functions, and LLVM will resolve references to each -appropriately.
-LLVM allows an explicit section to be specified for functions. If the target supports it, it will emit functions to the section specified.
@@ -749,9 +773,9 @@ a power of 2.The return type and each parameter of a function type may have a set of parameter attributes associated with them. Parameter attributes are used to communicate additional information about the result or parameters of - a function. Parameter attributes are considered to be part of the function - type so two functions types that differ only by the parameter attributes - are different function types.
+ a function. Parameter attributes are considered to be part of the function, + not of the function type, so functions with different parameter attributes + can have the same function type.Parameter attributes are simple keywords that follow the type specified. If multiple parameter attributes are needed, they are space separated. For @@ -759,22 +783,20 @@ a power of 2.
-%someFunc = i16 (i8 sext %someParam) zext -%someFunc = i16 (i8 zext %someParam) zext +declare i32 @printf(i8* noalias , ...) nounwind +declare i32 @atoi(i8*) nounwind readonly
Note that the two function types above are unique because the parameter has - a different attribute (sext in the first one, zext in the second). Also note - that the attribute for the function result (zext) comes immediately after the - argument list.
+Note that any attributes for the function result (nounwind, + readonly) come immediately after the argument list.
Currently, only the following parameter attributes are defined:
Each function may specify a garbage collector name, which is simply a +string.
+ +define void @f() gc "name" { ...The compiler declares the supported values of name. Specifying a +collector which will cause the compiler to alter its output in order to support +the named garbage collection algorithm.
+|
- i1 - i4 - i8 - i16 - i32 - i42 - i64 - i1942652 - |
-
- A boolean integer of 1 bit - A nibble sized integer of 4 bits. - A byte sized integer of 8 bits. - A half word sized integer of 16 bits. - A word sized integer of 32 bits. - An integer whose bit width is the answer. - A double word sized integer of 64 bits. - A really big integer of over 1 million bits. - |
+
| i1 | +a single-bit integer. | +
| i32 | +a 32-bit integer. | +
| i1942652 | +a really big integer of over 1 million bits. |
|
- [40 x i32 ] - [41 x i32 ] - [40 x i8] - |
-
- Array of 40 32-bit integer values. - Array of 41 32-bit integer values. - Array of 40 8-bit integer values. - |
+ [40 x i32] | +Array of 40 32-bit integer values. | +
| [41 x i32] | +Array of 41 32-bit integer values. | +||
| [4 x i8] | +Array of 4 8-bit integer values. |
Here are some examples of multidimensional arrays:
|
- [3 x [4 x i32]] - [12 x [10 x float]] - [2 x [3 x [4 x i16]]] - |
-
- 3x4 array of 32-bit integer values. - 12x10 array of single precision floating point values. - 2x3x4 array of 16-bit integer values. - |
+ [3 x [4 x i32]] | +3x4 array of 32-bit integer values. | +
| [12 x [10 x float]] | +12x10 array of single precision floating point values. | +||
| [2 x [3 x [4 x i16]]] | +2x3x4 array of 16-bit integer values. |
As in many languages, the pointer type represents a pointer or -reference to another object, which must live in memory.
+reference to another object, which must live in memory. Pointer types may have +an optional address space attribute defining the target-specific numbered +address space where the pointed-to object resides. The default address space is +zero.<type> *
|
- [4x i32]* - i32 (i32 *) * - |
-
- A pointer to array of
- four i32 values - A pointer to a [4x i32]* |
+ A pointer to array of four i32 values. | +
| i32 (i32 *) * | + A pointer to a function that takes an i32*, returning an
- i32. - |
+ i32.
+ |
| i32 addrspace(5)* | +A pointer to an i32 value + that resides in address space #5. |
|
- <4 x i32> - <8 x float> - <2 x i64> - |
-
- Vector of 4 32-bit integer values. - Vector of 8 floating-point values. - Vector of 2 64-bit integer values. - |
+ <4 x i32> | +Vector of 4 32-bit integer values. | +
| <8 x float> | +Vector of 8 32-bit floating-point values. | +||
| <2 x i64> | +Vector of 2 64-bit integer values. |
Opaque types are used to represent unknown types in the system. This -corresponds (for example) to the C notion of a foward declared structure type. +corresponds (for example) to the C notion of a forward declared structure type. In LLVM, opaque types can eventually be resolved to any type (not just a structure type).
@@ -1295,12 +1342,8 @@ structure type).| - opaque - | -
- An opaque type. - |
+ opaque | +An opaque type. |
The two arguments to the 'urem' instruction must be integer values. Both arguments must have identical -types.
+types. This instruction can also take vector versions +of the values in which case the elements must be integers.This instruction returns the unsigned integer remainder of a division. This instruction always performs an unsigned division to get the remainder, @@ -2094,7 +2146,10 @@ Instruction
The 'srem' instruction returns the remainder from the -signed division of its two operands.
+signed division of its two operands. This instruction can also take +vector versions of the values in which case +the elements must be integers. +The two arguments to the 'srem' instruction must be integer values. Both arguments must have identical @@ -2126,7 +2181,8 @@ division of its two operands.
The two arguments to the 'frem' instruction must be floating point values. Both arguments must have -identical types.
+identical types. This instruction can also take vector +versions of floating point values.This instruction returns the remainder of a division.
<result> = shl <ty> <var1>, <var2> ; yields {ty}:result
+
The 'shl' instruction returns the first operand shifted to the left a specified number of bits.
+Both arguments to the 'shl' instruction must be the same integer type.
+The value produced is var1 * 2var2.
+ +The value produced is var1 * 2var2. If +var2 is (statically or dynamically) equal to or larger than the number +of bits in var1, the result is undefined.
+
<result> = shl i32 4, %var ; yields {i32}: 4 << %var
<result> = shl i32 4, 2 ; yields {i32}: 16
<result> = shl i32 1, 10 ; yields {i32}: 1024
+ <result> = shl i32 1, 32 ; undefined
@@ -2184,9 +2250,11 @@ operand shifted to the right a specified number of bits with zero fill.
integer type.
This instruction always performs a logical shift right operation. The most significant bits of the result will be filled with zero bits after the -shift.
+shift. If var2 is (statically or dynamically) equal to or larger than +the number of bits in var1, the result is undefined.
@@ -2194,6 +2262,7 @@ shift.
<result> = lshr i32 4, 2 ; yields {i32}:result = 1
<result> = lshr i8 4, 3 ; yields {i8}:result = 0
<result> = lshr i8 -2, 1 ; yields {i8}:result = 0x7FFFFFFF
+ <result> = lshr i32 1, 32 ; undefined
@@ -2217,7 +2286,9 @@ operand shifted to the right a specified number of bits with sign extension.
This instruction always performs an arithmetic shift right operation, The most significant bits of the result will be filled with the sign bit -of var1.
+of var1. If var2 is (statically or dynamically) equal to or +larger than the number of bits in var1, the result is undefined. +
@@ -2225,6 +2296,7 @@ of var1.
<result> = ashr i32 4, 2 ; yields {i32}:result = 1
<result> = ashr i8 4, 3 ; yields {i8}:result = 0
<result> = ashr i8 -2, 1 ; yields {i8}:result = -1
+ <result> = ashr i32 1, 32 ; undefined
@@ -2586,7 +2658,8 @@ allocate, and free memory in LLVM.
The 'malloc' instruction allocates memory from the system -heap and returns a pointer to it.
+heap and returns a pointer to it. The object is always allocated in the generic +address space (address space zero).The 'alloca' instruction allocates memory on the stack frame of the currently executing function, to be automatically released when this function -returns to its caller.
+returns to its caller. The object is always allocated in the generic address +space (address space zero).%ptr = alloca i32 ; yields {i32*}:ptr - store i32 3, i32* %ptr ; yields {void} - %val = load i32* %ptr ; yields {i32}:val = i32 3 + store i32 3, i32* %ptr ; yields {void} + %val = load i32* %ptr ; yields {i32}:val = i32 3@@ -3079,34 +3152,32 @@ used to make a no-op cast because it always changes bits. Use
- <result> = fp2uint <ty> <value> to <ty2> ; yields ty2 + <result> = fptoui <ty> <value> to <ty2> ; yields ty2
The 'fp2uint' converts a floating point value to its +
The 'fptoui' converts a floating point value to its unsigned integer equivalent of type ty2.
The 'fp2uint' instruction takes a value to cast, which must be a -floating point value, and a type to cast it to, which -must be an integer type.
+The 'fptoui' instruction takes a value to cast, which must be a +scalar or vector floating point value, and a type +to cast it to ty2, which must be an integer +type. If ty is a vector floating point type, ty2 must be a +vector integer type with the same number of elements as ty
The 'fp2uint' instruction converts its +
The 'fptoui' instruction converts its floating point operand into the nearest (rounding towards zero) unsigned integer value. If the value cannot fit in ty2, the results are undefined.
-When converting to i1, the conversion is done as a comparison against -zero. If the value was zero, the i1 result will be false. -If the value was non-zero, the i1 result will be true.
-- %X = fp2uint double 123.0 to i32 ; yields i32:123 - %Y = fp2uint float 1.0E+300 to i1 ; yields i1:true - %X = fp2uint float 1.04E+17 to i8 ; yields undefined:1 + %X = fptoui double 123.0 to i32 ; yields i32:123 + %Y = fptoui float 1.0E+300 to i1 ; yields undefined:1 + %X = fptoui float 1.04E+17 to i8 ; yields undefined:1@@ -3126,11 +3197,12 @@ If the value was non-zero, the i1 result will be true. floating point value to type ty2. -
The 'fptosi' instruction takes a value to cast, which must be a -floating point value, and a type to cast it to, which -must also be an integer type.
+scalar or vector floating point value, and a type +to cast it to ty2, which must be an integer +type. If ty is a vector floating point type, ty2 must be a +vector integer type with the same number of elements as tyThe 'fptosi' instruction converts its @@ -3138,14 +3210,10 @@ must also be an integer type.
towards zero) signed integer value. If the value cannot fit in ty2, the results are undefined. -When converting to i1, the conversion is done as a comparison against -zero. If the value was zero, the i1 result will be false. -If the value was non-zero, the i1 result will be true.
-%X = fptosi double -123.0 to i32 ; yields i32:-123 - %Y = fptosi float 1.0E-247 to i1 ; yields i1:true + %Y = fptosi float 1.0E-247 to i1 ; yields undefined:1 %X = fptosi float 1.04E+17 to i8 ; yields undefined:1@@ -3165,18 +3233,18 @@ If the value was non-zero, the i1 result will be true.
The 'uitofp' instruction regards value as an unsigned integer and converts that value to the ty2 type.
-The 'uitofp' instruction takes a value to cast, which must be an -integer value, and a type to cast it to, which must -be a floating point type.
+The 'uitofp' instruction takes a value to cast, which must be a +scalar or vector integer value, and a type to cast it +to ty2, which must be an floating point +type. If ty is a vector integer type, ty2 must be a vector +floating point type with the same number of elements as ty
The 'uitofp' instruction interprets its operand as an unsigned integer quantity and converts it to the corresponding floating point value. If the value cannot fit in the floating point value, the results are undefined.
-%X = uitofp i32 257 to float ; yields float:257.0 @@ -3200,9 +3268,11 @@ the value cannot fit in the floating point value, the results are undefined. integer and converts that value to the ty2 type.Arguments:
-The 'sitofp' instruction takes a value to cast, which must be an -integer value, and a type to cast it to, which must be -a floating point type.
+The 'sitofp' instruction takes a value to cast, which must be a +scalar or vector integer value, and a type to cast it +to ty2, which must be an floating point +type. If ty is a vector integer type, ty2 must be a vector +floating point type with the same number of elements as ty
Semantics:
The 'sitofp' instruction interprets its operand as a signed @@ -3560,7 +3630,7 @@ value argument; otherwise, it returns the second value argument.
Syntax:
- <result> = [tail] call [cconv] <ty>* <fnptrval>(<param list>) + <result> = [tail] call [cconv] <ty> [<fnty>*] <fnptrval>(<param list>)Overview:
@@ -3585,10 +3655,15 @@ value argument; otherwise, it returns the second value argument. to using C calling conventions.
'ty': shall be the signature of the pointer to function value - being invoked. The argument types must match the types implied by this - signature. This type can be omitted if the function is not varargs and - if the function type does not return a pointer to a function.
+'ty': the type of the call instruction itself which is also + the type of the return value. Functions that return no value are marked + void.
+'fnty': shall be the signature of the pointer to function + value being invoked. The argument types must match the types implied by + this signature. This type can be omitted if the function is not varargs + and if the function type does not return a pointer to a function.
'fnptrval': An LLVM value containing a pointer to a function to @@ -3618,10 +3693,11 @@ the invoke instruction.
- %retval = call i32 %test(i32 %argc) - call i32(i8 *, ...) *%printf(i8 * %msg, i32 12, i8 42); - %X = tail call i32 %foo() - %Y = tail call fastcc i32 %foo() + %retval = call i32 @test(i32 %argc) + call i32 (i8 *, ...)* @printf(i8 * %msg, i32 12, i8 42); + %X = tail call i32 @foo() + %Y = tail call fastcc i32 @foo() + %Z = call void %foo(i8 97 signext)@@ -3684,7 +3760,7 @@ argument. well known names and semantics and are required to follow certain restrictions. Overall, these intrinsics represent an extension mechanism for the LLVM language that does not require changing all of the transformations in LLVM when -adding to the language (or the bytecode reader/writer, the parser, etc...). +adding to the language (or the bitcode reader/writer, the parser, etc...).
Intrinsic function names must all start with an "llvm." prefix. This prefix is reserved in LLVM for intrinsic names; thus, function names may not @@ -3695,17 +3771,27 @@ of an intrinsic function. Additionally, because intrinsic functions are part of the LLVM language, it is required if any are added that they be documented here.
-Some intrinsic functions can be overloaded, i.e., the intrinsic represents -a family of functions that perform the same operation but on different data -types. This is most frequent with the integer types. Since LLVM can represent -over 8 million different integer types, there is a way to declare an intrinsic -that can be overloaded based on its arguments. Such an intrinsic will have the -names of its argument types encoded into its function name, each -preceded by a period. For example, the llvm.ctpop function can take an -integer of any width. This leads to a family of functions such as -i32 @llvm.ctpop.i8(i8 %val) and i32 @llvm.ctpop.i29(i29 %val). -
- +Some intrinsic functions can be overloaded, i.e., the intrinsic represents +a family of functions that perform the same operation but on different data +types. Because LLVM can represent over 8 million different integer types, +overloading is used commonly to allow an intrinsic function to operate on any +integer type. One or more of the argument types or the result type can be +overloaded to accept any integer type. Argument types may also be defined as +exactly matching a previous argument's type or the result type. This allows an +intrinsic function which accepts multiple arguments, but needs all of them to +be of the same type, to only be overloaded with respect to a single argument or +the result.
+ +Overloaded intrinsics will have the names of its overloaded argument types +encoded into its function name, each preceded by a period. Only those types +which are overloaded result in a name suffix. Arguments whose type is matched +against another type do not. For example, the llvm.ctpop function can +take an integer of any width and returns an integer of exactly the same integer +width. This leads to a family of functions such as +i8 @llvm.ctpop.i8(i8 %val) and i29 @llvm.ctpop.i29(i29 %val). +Only one type, the return type, is overloaded, and only one type suffix is +required. Because the argument's type is matched against the return type, it +does not require its own name suffix.
To learn how to add an intrinsic function, please see the Extending LLVM Guide. @@ -3875,6 +3961,10 @@ Front-ends for type-safe garbage collected languages should generate these intrinsics to make use of the LLVM garbage collectors. For more details, see Accurate Garbage Collection with LLVM.
+ +The garbage collection intrinsics only operate on objects in the generic + address space (address space zero).
+ @@ -3887,7 +3977,7 @@ href="GarbageCollection.html">Accurate Garbage Collection with LLVM.- declare void @llvm.gcroot(<ty>** %ptrloc, <ty2>* %metadata) + declare void @llvm.gcroot(i8** %ptrloc, i8* %metadata)
At runtime, a call to this intrinsics stores a null pointer into the "ptrloc" location. At compile-time, the code generator generates information to allow -the runtime to find the pointer at GC safe points. -
+the runtime to find the pointer at GC safe points. The 'llvm.gcroot' +intrinsic may only be used in a function which specifies a GC +algorithm. @@ -3921,7 +4012,7 @@ the runtime to find the pointer at GC safe points.- declare i8 * @llvm.gcread(i8 * %ObjPtr, i8 ** %Ptr) + declare i8* @llvm.gcread(i8* %ObjPtr, i8** %Ptr)
The 'llvm.gcread' intrinsic has the same semantics as a load instruction, but may be replaced with substantially more complex code by the -garbage collector runtime, as needed.
+garbage collector runtime, as needed. The 'llvm.gcread' intrinsic +may only be used in a function which specifies a GC +algorithm. @@ -3956,7 +4049,7 @@ garbage collector runtime, as needed.- declare void @llvm.gcwrite(i8 * %P1, i8 * %Obj, i8 ** %P2) + declare void @llvm.gcwrite(i8* %P1, i8* %Obj, i8** %P2)
The 'llvm.gcwrite' intrinsic has the same semantics as a store instruction, but may be replaced with substantially more complex code by the -garbage collector runtime, as needed.
+garbage collector runtime, as needed. The 'llvm.gcwrite' intrinsic +may only be used in a function which specifies a GC +algorithm. @@ -4049,7 +4144,7 @@ source-language caller.- declare i8 *@llvm.frameaddress(i32 <level>) + declare i8 *@llvm.frameaddress(i32 <level>)
- declare i8 *@llvm.stacksave() + declare i8 *@llvm.stacksave()
- declare void @llvm.prefetch(i8 * <address>, - i32 <rw>, i32 <locality>) + declare void @llvm.prefetch(i8* <address>, i32 <rw>, i32 <locality>)
- declare void @llvm.pcmarker( i32 <id> ) + declare void @llvm.pcmarker(i32 <id>)
This is an overloaded intrinsic. You can use llvm.sqrt on any +floating point or vector of floating point type. Not all targets support all +types however.
- declare float @llvm.sqrt.f32(float %Val) - declare double @llvm.sqrt.f64(double %Val) + declare float @llvm.sqrt.f32(float %Val) + declare double @llvm.sqrt.f64(double %Val) + declare x86_fp80 @llvm.sqrt.f80(x86_fp80 %Val) + declare fp128 @llvm.sqrt.f128(fp128 %Val) + declare ppc_fp128 @llvm.sqrt.ppcf128(ppc_fp128 %Val)
The 'llvm.sqrt' intrinsics return the sqrt of the specified operand, -returning the same value as the libm 'sqrt' function would. Unlike +returning the same value as the libm 'sqrt' functions would. Unlike sqrt in libm, however, llvm.sqrt has undefined behavior for negative numbers (which allows for better optimization).
@@ -4476,7 +4576,7 @@ The argument and return value are floating point numbers of the same type.-This function returns the sqrt of the specified operand if it is a positive +This function returns the sqrt of the specified operand if it is a nonnegative floating point number.
This is an overloaded intrinsic. You can use llvm.powi on any +floating point or vector of floating point type. Not all targets support all +types however.
- declare float @llvm.powi.f32(float %Val, i32 %power) - declare double @llvm.powi.f64(double %Val, i32 %power) + declare float @llvm.powi.f32(float %Val, i32 %power) + declare double @llvm.powi.f64(double %Val, i32 %power) + declare x86_fp80 @llvm.powi.f80(x86_fp80 %Val, i32 %power) + declare fp128 @llvm.powi.f128(fp128 %Val, i32 %power) + declare ppc_fp128 @llvm.powi.ppcf128(ppc_fp128 %Val, i32 %power)
The 'llvm.powi.*' intrinsics return the first operand raised to the specified (positive or negative) power. The order of evaluation of -multiplications is not defined. +multiplications is not defined. When a vector of floating point type is +used, the second argument remains a scalar integer value.
This is an overloaded intrinsic. You can use llvm.sin on any +floating point or vector of floating point type. Not all targets support all +types however. +
+ declare float @llvm.sin.f32(float %Val) + declare double @llvm.sin.f64(double %Val) + declare x86_fp80 @llvm.sin.f80(x86_fp80 %Val) + declare fp128 @llvm.sin.f128(fp128 %Val) + declare ppc_fp128 @llvm.sin.ppcf128(ppc_fp128 %Val) ++ +
+The 'llvm.sin.*' intrinsics return the sine of the operand. +
+ ++The argument and return value are floating point numbers of the same type. +
+ ++This function returns the sine of the specified operand, returning the +same values as the libm sin functions would, and handles error +conditions in the same way.
+This is an overloaded intrinsic. You can use llvm.cos on any +floating point or vector of floating point type. Not all targets support all +types however. +
+ declare float @llvm.cos.f32(float %Val) + declare double @llvm.cos.f64(double %Val) + declare x86_fp80 @llvm.cos.f80(x86_fp80 %Val) + declare fp128 @llvm.cos.f128(fp128 %Val) + declare ppc_fp128 @llvm.cos.ppcf128(ppc_fp128 %Val) ++ +
+The 'llvm.cos.*' intrinsics return the cosine of the operand. +
+ ++The argument and return value are floating point numbers of the same type. +
+ ++This function returns the cosine of the specified operand, returning the +same values as the libm cos functions would, and handles error +conditions in the same way.
+This is an overloaded intrinsic. You can use llvm.pow on any +floating point or vector of floating point type. Not all targets support all +types however. +
+ declare float @llvm.pow.f32(float %Val, float %Power) + declare double @llvm.pow.f64(double %Val, double %Power) + declare x86_fp80 @llvm.pow.f80(x86_fp80 %Val, x86_fp80 %Power) + declare fp128 @llvm.pow.f128(fp128 %Val, fp128 %Power) + declare ppc_fp128 @llvm.pow.ppcf128(ppc_fp128 %Val, ppc_fp128 Power) ++ +
+The 'llvm.pow.*' intrinsics return the first operand raised to the +specified (positive or negative) power. +
+ ++The second argument is a floating point power, and the first is a value to +raise to that power. +
+ ++This function returns the first value raised to the second power, +returning the +same values as the libm pow functions would, and handles error +conditions in the same way.
+This is an overloaded intrinsic function. You can use bswap on any integer -type that is an even number of bytes (i.e. BitWidth % 16 == 0). Note the suffix -that includes the type for the result and the operand. +type that is an even number of bytes (i.e. BitWidth % 16 == 0).
- declare i16 @llvm.bswap.i16.i16(i16 <id>) - declare i32 @llvm.bswap.i32.i32(i32 <id>) - declare i64 @llvm.bswap.i64.i64(i64 <id>) + declare i16 @llvm.bswap.i16(i16 <id>) + declare i32 @llvm.bswap.i32(i32 <id>) + declare i64 @llvm.bswap.i64(i64 <id>)
-The llvm.bswap.16.i16 intrinsic returns an i16 value that has the high +The llvm.bswap.i16 intrinsic returns an i16 value that has the high and low byte of the input i16 swapped. Similarly, the llvm.bswap.i32 intrinsic returns an i32 value that has the four bytes of the input i32 swapped, so that if the input bytes are numbered 0, 1, 2, 3 then the returned -i32 will have its bytes in 3, 2, 1, 0 order. The llvm.bswap.i48.i48, -llvm.bswap.i64.i64 and other intrinsics extend this concept to +i32 will have its bytes in 3, 2, 1, 0 order. The llvm.bswap.i48, +llvm.bswap.i64 and other intrinsics extend this concept to additional even-byte lengths (6 bytes, 8 bytes and more, respectively).
@@ -4581,11 +4807,11 @@ additional even-byte lengths (6 bytes, 8 bytes and more, respectively).This is an overloaded intrinsic. You can use llvm.ctpop on any integer bit width. Not all targets support all bit widths however.
- declare i32 @llvm.ctpop.i8 (i8 <src>) - declare i32 @llvm.ctpop.i16(i16 <src>) + declare i8 @llvm.ctpop.i8 (i8 <src>) + declare i16 @llvm.ctpop.i16(i16 <src>) declare i32 @llvm.ctpop.i32(i32 <src>) - declare i32 @llvm.ctpop.i64(i64 <src>) - declare i32 @llvm.ctpop.i256(i256 <src>) + declare i64 @llvm.ctpop.i64(i64 <src>) + declare i256 @llvm.ctpop.i256(i256 <src>)
This is an overloaded intrinsic. You can use llvm.ctlz on any integer bit width. Not all targets support all bit widths however.
- declare i32 @llvm.ctlz.i8 (i8 <src>) - declare i32 @llvm.ctlz.i16(i16 <src>) + declare i8 @llvm.ctlz.i8 (i8 <src>) + declare i16 @llvm.ctlz.i16(i16 <src>) declare i32 @llvm.ctlz.i32(i32 <src>) - declare i32 @llvm.ctlz.i64(i64 <src>) - declare i32 @llvm.ctlz.i256(i256 <src>) + declare i64 @llvm.ctlz.i64(i64 <src>) + declare i256 @llvm.ctlz.i256(i256 <src>)
This is an overloaded intrinsic. You can use llvm.cttz on any integer bit width. Not all targets support all bit widths however.
- declare i32 @llvm.cttz.i8 (i8 <src>) - declare i32 @llvm.cttz.i16(i16 <src>) + declare i8 @llvm.cttz.i8 (i8 <src>) + declare i16 @llvm.cttz.i16(i16 <src>) declare i32 @llvm.cttz.i32(i32 <src>) - declare i32 @llvm.cttz.i64(i64 <src>) - declare i32 @llvm.cttz.i256(i256 <src>) + declare i64 @llvm.cttz.i64(i64 <src>) + declare i256 @llvm.cttz.i256(i256 <src>)
This is an overloaded intrinsic. You can use llvm.part.select on any integer bit width.
- declare i17 @llvm.part.select.i17.i17 (i17 %val, i32 %loBit, i32 %hiBit) - declare i29 @llvm.part.select.i29.i29 (i29 %val, i32 %loBit, i32 %hiBit) + declare i17 @llvm.part.select.i17 (i17 %val, i32 %loBit, i32 %hiBit) + declare i29 @llvm.part.select.i29 (i29 %val, i32 %loBit, i32 %hiBit)
This is an overloaded intrinsic. You can use llvm.part.set on any integer bit width.
- declare i17 @llvm.part.set.i17.i17.i9 (i17 %val, i9 %repl, i32 %lo, i32 %hi) - declare i29 @llvm.part.set.i29.i29.i9 (i29 %val, i9 %repl, i32 %lo, i32 %hi) + declare i17 @llvm.part.set.i17.i9 (i17 %val, i9 %repl, i32 %lo, i32 %hi) + declare i29 @llvm.part.set.i29.i9 (i29 %val, i9 %repl, i32 %lo, i32 %hi)
+ This intrinsic makes it possible to excise one parameter, marked with + the nest attribute, from a function. The result is a callable + function pointer lacking the nest parameter - the caller does not need + to provide a value for it. Instead, the value to use is stored in + advance in a "trampoline", a block of memory usually allocated + on the stack, which also contains code to splice the nest value into the + argument list. This is used to implement the GCC nested function address + extension. +
++ For example, if the function is + i32 f(i8* nest %c, i32 %x, i32 %y) then the resulting function + pointer has signature i32 (i32, i32)*. It can be created as follows:
++ %tramp = alloca [10 x i8], align 4 ; size and alignment only correct for X86 + %tramp1 = getelementptr [10 x i8]* %tramp, i32 0, i32 0 + %p = call i8* @llvm.init.trampoline( i8* %tramp1, i8* bitcast (i32 (i8* nest , i32, i32)* @f to i8*), i8* %nval ) + %fp = bitcast i8* %p to i32 (i32, i32)* ++
The call %val = call i32 %fp( i32 %x, i32 %y ) is then equivalent + to %val = call i32 %f( i8* %nval, i32 %x, i32 %y ).
++declare i8* @llvm.init.trampoline(i8* <tramp>, i8* <func>, i8* <nval>) ++
+ This fills the memory pointed to by tramp with code + and returns a function pointer suitable for executing it. +
++ The llvm.init.trampoline intrinsic takes three arguments, all + pointers. The tramp argument must point to a sufficiently large + and sufficiently aligned block of memory; this memory is written to by the + intrinsic. Note that the size and the alignment are target-specific - LLVM + currently provides no portable way of determining them, so a front-end that + generates this intrinsic needs to have some target-specific knowledge. + The func argument must hold a function bitcast to an i8*. +
++ The block of memory pointed to by tramp is filled with target + dependent code, turning it into a function. A pointer to this function is + returned, but needs to be bitcast to an + appropriate function pointer type + before being called. The new function's signature is the same as that of + func with any arguments marked with the nest attribute + removed. At most one such nest argument is allowed, and it must be + of pointer type. Calling the new function is equivalent to calling + func with the same argument list, but with nval used for the + missing nest argument. If, after calling + llvm.init.trampoline, the memory pointed to by tramp is + modified, then the effect of any later call to the returned function pointer is + undefined. +
+This class of intrinsics is designed to be generic and has +no specific purpose.
++ declare void @llvm.var.annotation(i8* <val>, i8* <str>, i8* <str>, i32 <int> ) ++ +
+The 'llvm.var.annotation' intrinsic +
+ ++The first argument is a pointer to a value, the second is a pointer to a +global string, the third is a pointer to a global string which is the source +file name, and the last argument is the line number. +
+ ++This intrinsic allows annotation of local variables with arbitrary strings. +This can be useful for special purpose optimizations that want to look for these + annotations. These have no other defined use, they are ignored by code + generation and optimization. +
This is an overloaded intrinsic. You can use 'llvm.annotation' on +any integer bit width. +
++ declare i8 @llvm.annotation.i8(i8 <val>, i8* <str>, i8* <str>, i32 <int> ) + declare i16 @llvm.annotation.i16(i16 <val>, i8* <str>, i8* <str>, i32 <int> ) + declare i32 @llvm.annotation.i32(i32 <val>, i8* <str>, i8* <str>, i32 <int> ) + declare i64 @llvm.annotation.i64(i64 <val>, i8* <str>, i8* <str>, i32 <int> ) + declare i256 @llvm.annotation.i256(i256 <val>, i8* <str>, i8* <str>, i32 <int> ) ++ +
+The 'llvm.annotation' intrinsic. +
+ ++The first argument is an integer value (result of some expression), +the second is a pointer to a global string, the third is a pointer to a global +string which is the source file name, and the last argument is the line number. +It returns the value of the first argument. +
+ ++This intrinsic allows annotations to be put on arbitrary expressions +with arbitrary strings. This can be useful for special purpose optimizations +that want to look for these annotations. These have no other defined use, they +are ignored by code generation and optimization. +