X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;ds=sidebyside;f=docs%2FLangRef.html;h=d9d5ca837359a447d76a5d2f857a83ee59eafc5e;hb=15bfd89b995e9b8a4fe4f321b3ea29b546c94bac;hp=308dd207e5d51158a2f2ac5d77047068d19918d1;hpb=cc68939ba63e840b317789e10c1fb4645d95c328;p=oota-llvm.git diff --git a/docs/LangRef.html b/docs/LangRef.html index 308dd207e5d..d9d5ca83735 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -26,19 +26,24 @@
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.
@@ -673,12 +687,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 @@ -761,9 +776,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 @@ -771,49 +786,88 @@ a power of 2.
-%someFunc = i16 (i8 signext %someParam) zeroext -%someFunc = i16 (i8 zeroext %someParam) zeroext +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 (signext in the first one, zeroext in - the second). Also note that the attribute for the function result - (zeroext) 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.
+The primitive types are the fundamental building blocks of the LLVM -system. The current set of primitive types is as follows:
- -
-
|
-
-
|
-
These different primitive types fall into a few useful +
The types fall into a few useful classifications:
Classification | Types | ||
---|---|---|---|
integer | +integer | i1, i2, i3, ... i8, ... i16, ... i32, ... i64, ... | |
floating point | -float, double | +floating point | +float, double, x86_fp80, fp128, ppc_fp128 |
first class | -i1, ..., float, double, - pointer,vector + | integer, + floating point, + pointer, + vector | |
primitive | +label, + void, + integer, + floating point. | +||
derived | +integer, + array, + function, + pointer, + structure, + packed structure, + vector, + opaque. + |
The primitive types are the fundamental building blocks of the LLVM +system.
+ +Type | Description |
---|---|
float | 32-bit floating point value |
double | 64-bit floating point value |
fp128 | 128-bit floating point value (112-bit mantissa) |
x86_fp80 | 80-bit floating point value (X87) |
ppc_fp128 | 128-bit floating point value (two 64-bits) |
The void type does not represent any value and has no size.
+ ++ void ++
The label type represents code labels.
+ ++ label ++
- 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).
@@ -1310,12 +1404,8 @@ structure type).- opaque - | -
- An opaque type. - |
+ opaque | +An opaque type. |
The value produced is the integer or floating point sum of the two operands.
+If an integer sum has unsigned overflow, the result returned is the +mathematical result modulo 2n, where n is the bit width of +the result.
+Because LLVM integers use a two's complement representation, this +instruction is appropriate for both signed and unsigned integers.
<result> = add i32 4, %var ; yields {i32}:result = 4 + %var@@ -1978,6 +2081,11 @@ Both arguments must have identical types.
The value produced is the integer or floating point difference of the two operands.
+If an integer difference has unsigned overflow, the result returned is the +mathematical result modulo 2n, where n is the bit width of +the result.
+Because LLVM integers use a two's complement representation, this +instruction is appropriate for both signed and unsigned integers.
<result> = sub i32 4, %var ; yields {i32}:result = 4 - %var @@ -2003,9 +2111,15 @@ Both arguments must have identical types.Semantics:
The value produced is the integer or floating point product of the two operands.
-Because the operands are the same width, the result of an integer -multiplication is the same whether the operands should be deemed unsigned or -signed.
+If the result of an integer multiplication has unsigned overflow, +the result returned is the mathematical result modulo +2n, where n is the bit width of the result.
+Because LLVM integers use a two's complement representation, and the +result is the same width as the operands, this instruction returns the +correct result for both signed and unsigned integers. If a full product +(e.g. i32xi32->i64) is needed, the operands +should be sign-extended or zero-extended as appropriate to the +width of the full product.
Example:
<result> = mul i32 4, %var ; yields {i32}:result = 4 * %var@@ -2026,9 +2140,10 @@ operands. types. This instruction can also take vector versions of the values in which case the elements must be integers.Semantics:
-The value produced is the unsigned integer quotient of the two operands. This -instruction always performs an unsigned division operation, regardless of -whether the arguments are unsigned or not.
+The value produced is the unsigned integer quotient of the two operands.
+Note that unsigned integer division and signed integer division are distinct +operations; for signed integer division, use 'sdiv'.
+Division by zero leads to undefined behavior.
Example:
<result> = udiv i32 4, %var ; yields {i32}:result = 4 / %var@@ -2049,9 +2164,12 @@ operands. types. This instruction can also take vector versions of the values in which case the elements must be integers.Semantics:
-The value produced is the signed integer quotient of the two operands. This -instruction always performs a signed division operation, regardless of whether -the arguments are signed or not.
+The value produced is the signed integer quotient of the two operands.
+Note that signed integer division and unsigned integer division are distinct +operations; for unsigned integer division, use 'udiv'.
+Division by zero leads to undefined behavior. Overflow also leads to +undefined behavior; this is a rare case, but can occur, for example, +by doing a 32-bit division of -2147483648 by -1.
Example:
<result> = sdiv i32 4, %var ; yields {i32}:result = 4 / %var@@ -2090,11 +2208,15 @@ unsigned division of its two arguments.Arguments:
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.Semantics:
This instruction returns the unsigned integer remainder of a division. This instruction always performs an unsigned division to get the remainder, regardless of whether the arguments are unsigned or not.
+Note that unsigned integer remainder and signed integer remainder are +distinct operations; for signed integer remainder, use 'srem'.
+Taking the remainder of a division by zero leads to undefined behavior.
Example:
<result> = urem i32 4, %var ; yields {i32}:result = 4 % %var@@ -2109,7 +2231,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 @@ -2123,6 +2248,14 @@ a value. For more information about the difference, see . For a table of how this is implemented in various languages, please see Wikipedia: modulo operation.
+Note that signed integer remainder and unsigned integer remainder are +distinct operations; for unsigned integer remainder, use 'urem'.
+Taking the remainder of a division by zero leads to undefined behavior. +Overflow also leads to undefined behavior; this is a rare case, but can occur, +for example, by taking the remainder of a 32-bit division of -2147483648 by -1. +(The remainder doesn't actually overflow, but this rule lets srem be +implemented using instructions that return both the result of the division +and the remainder.)
<result> = srem i32 4, %var ; yields {i32}:result = 4 % %var@@ -2141,7 +2274,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@@ -2199,9 +2343,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.@@ -2209,6 +2355,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@@ -2232,7 +2379,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. +@@ -2240,6 +2389,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@@ -2601,7 +2751,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).'type' must be a sized type.
@@ -2688,17 +2839,18 @@ after this instruction executes.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).The 'alloca' instruction allocates sizeof(<type>)*NumElements bytes of memory on the runtime stack, returning a pointer of the -appropriate type to the program. If "NumElements" is specified, it is the -number of elements allocated. If an alignment is specified, the value result -of the allocation is guaranteed to be aligned to at least that boundary. If -not specified, or if zero, the target can choose to align the allocation on any -convenient boundary.
+appropriate type to the program. If "NumElements" is specified, it is the +number of elements allocated, otherwise "NumElements" is defaulted to be one. +If an alignment is specified, the value result of the allocation is guaranteed +to be aligned to at least that boundary. If not specified, or if zero, the target +can choose to align the allocation on any convenient boundary.'type' may be any sized type.
@@ -2737,6 +2889,16 @@ marked as volatile, then the optimizer is not allowed to modify the number or order of execution of this load with other volatile load and store instructions. ++The optional "align" argument specifies the alignment of the operation +(that is, the alignment of the memory address). A value of 0 or an +omitted "align" argument means that the operation has the preferential +alignment for the target. It is the responsibility of the code emitter +to ensure that the alignment information is correct. Overestimating +the alignment results in an undefined behavior. Underestimating the +alignment may produce less efficient code. An alignment of 1 is always +safe. +
The location of memory pointed to is loaded.
+The optional "align" argument specifies the alignment of the operation +(that is, the alignment of the memory address). A value of 0 or an +omitted "align" argument means that the operation has the preferential +alignment for the target. It is the responsibility of the code emitter +to ensure that the alignment information is correct. Overestimating +the alignment results in an undefined behavior. Underestimating the +alignment may produce less efficient code. An alignment of 1 is always +safe. +
The contents of memory are updated to contain '<value>' at the location specified by the '<pointer>' operand.
%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@@ -3104,8 +3275,10 @@ unsigned integer equivalent of type ty2.
The 'fptoui' 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.
+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 'fptoui' instruction converts its @@ -3137,11 +3310,12 @@ the results are undefined.
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 @@ -3172,18 +3346,18 @@ the results are undefined.
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 @@ -3207,9 +3381,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 @@ -3898,6 +4074,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).
+ @@ -3928,8 +4108,9 @@ value address) contains the meta-data to be associated with the root.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. @@ -3964,7 +4145,9 @@ null).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. @@ -3999,7 +4182,9 @@ null.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. @@ -4379,7 +4564,7 @@ be set to 0 or 1.The 'llvm.memmove.*' intrinsics move a block of memory from the source location to the destination location. It is similar to the -'llvm.memcmp' intrinsic but allows the two memory locations to overlap. +'llvm.memcpy' intrinsic but allows the two memory locations to overlap.
@@ -4476,7 +4661,8 @@ this can be specified as the fourth argument, otherwise it should be set to 0 or
Syntax:
This is an overloaded intrinsic. You can use llvm.sqrt on any -floating point type. Not all targets support all types however. +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) @@ -4489,9 +4675,11 @@ floating point type. Not all targets support all types however.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). +negative numbers other than -0.0 (which allows for better optimization, because +there is no need to worry about errno being set). llvm.sqrt(-0.0) is +defined to return -0.0 like IEEE sqrt.
Arguments:
@@ -4517,7 +4705,8 @@ floating point number.Syntax:
This is an overloaded intrinsic. You can use llvm.powi on any -floating point type. Not all targets support all types however. +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) @@ -4531,7 +4720,8 @@ floating point type. Not all targets support all types however.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.
Arguments:
@@ -4548,6 +4738,126 @@ This function returns the first value raised to the second power with an unspecified sequence of rounding operations. + + + ++ ++ + + + +Syntax:
+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) ++ +Overview:
+ ++The 'llvm.sin.*' intrinsics return the sine of the operand. +
+ +Arguments:
+ ++The argument and return value are floating point numbers of the same type. +
+ +Semantics:
+ ++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.
++ ++ + + + +Syntax:
+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) ++ +Overview:
+ ++The 'llvm.cos.*' intrinsics return the cosine of the operand. +
+ +Arguments:
+ ++The argument and return value are floating point numbers of the same type. +
+ +Semantics:
+ ++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.
++ ++Syntax:
+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) ++ +Overview:
+ ++The 'llvm.pow.*' intrinsics return the first operand raised to the +specified (positive or negative) power. +
+ +Arguments:
+ ++The second argument is a floating point power, and the first is a value to +raise to that power. +
+ +Semantics:
+ ++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.
+@@ -4961,10 +5271,11 @@ file name, and the last argument is the line number.@@ -5010,17 +5321,51 @@ that want to look for these annotations. These have no other defined use, they are ignored by code generation and optimization. + + + +Semantics:
-This intrinsic allows annotation of local variables with arbitrary strings. +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. +annotations. These have no other defined use, they are ignored by code +generation and optimization. +
+ ++Syntax:
++ declare void @llvm.trap() ++ +Overview:
+ ++The 'llvm.trap' intrinsic +
+ +Arguments:
+ ++None +
+ +Semantics:
+ ++This intrinsics is lowered to the target dependent trap instruction. If the +target does not have a trap instruction, this intrinsic will be lowered to the +call of the abort() function. +
+
![]()
+ src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"> Chris Lattner
The LLVM Compiler Infrastructure
Last modified: $Date$ +