From 721c201bd55ffb73cb2ba8d39e0570fa38c44e15 Mon Sep 17 00:00:00 2001 From: dim Date: Wed, 15 Aug 2012 19:34:23 +0000 Subject: Vendor import of llvm trunk r161861: http://llvm.org/svn/llvm-project/llvm/trunk@161861 --- docs/LangRef.html | 271 ++++++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 244 insertions(+), 27 deletions(-) (limited to 'docs/LangRef.html') diff --git a/docs/LangRef.html b/docs/LangRef.html index 5261230..946380e 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -7,7 +7,7 @@ - + @@ -257,6 +257,8 @@

'llvm.fabs.*' Intrinsic

'llvm.floor.*' Intrinsic

Bit Manipulation Intrinsics @@ -277,6 +279,11 @@

'llvm.umul.with.overflow.* Intrinsics

Specialised Arithmetic Intrinsics +

'llvm.fmuladd Intrinsic

Half Precision Floating Point Intrinsics

'llvm.convert.to.fp16' Intrinsic

llvm.annotation.*

'llvm.trap' Intrinsic
+ 'llvm.debugtrap' Intrinsic
'llvm.stackprotector' Intrinsic
+
'llvm.objectsize' Intrinsic
+
'llvm.expect' Intrinsic
+ 'llvm.donothing' Intrinsic

@@ -831,9 +842,32 @@ define i32 @main() { ; i32()*

Global variables define regions of memory allocated at compilation time instead of run-time. Global variables may optionally be initialized, may have an explicit section to be placed in, and may have an optional explicit - alignment specified. A variable may be defined as "thread_local", which + alignment specified.

+ +

A variable may be defined as thread_local, which means that it will not be shared by threads (each thread will have a - separated copy of the variable). A variable may be defined as a global + separated copy of the variable). Not all targets support thread-local + variables. Optionally, a TLS model may be specified:

+ +

localdynamic:: For variables that are only used within the current shared library.
initialexec:: For variables in modules that will not be loaded dynamically.
localexec:: For variables defined in the executable and only used within it.

+ +

The models correspond to the ELF TLS models; see + ELF + Handling For Thread-Local Storage for more information on under which + circumstances the different models may be used. The target may choose a + different TLS model if the specified model is not supported, or if a better + choice of model can be made.

+ +

A variable may be defined as a global "constant," which indicates that the contents of the variable will never be modified (enabling better optimization, allowing the global data to be placed in the read-only section of an executable, etc). @@ -886,6 +920,13 @@ define i32 @main() { ; i32()* @G = addrspace(5) constant float 1.0, section "foo", align 4 +

The following example defines a thread-local global with + the initialexec TLS model:

+ +

+@G = thread_local(initialexec) global i32 0, align 4
+

+ @@ -1048,7 +1089,7 @@ declare signext i8 @returns_signed_char() value to the function. The attribute implies that a hidden copy of the pointee is made between the caller and the callee, so the callee is unable to - modify the value in the callee. This attribute is only valid on LLVM + modify the value in the caller. This attribute is only valid on LLVM pointer arguments. It is generally used to pass structs and arrays by value, but is also valid on pointers to scalars. The copy is considered to belong to the caller not the callee (for example, @@ -1167,6 +1208,13 @@ define void @f() optsize { ... } may make calls to the function faster, at the cost of extra program startup time if the function is not called during program startup. +

ia_nsdialect

This attribute indicates the associated inline assembly call is using a + non-standard assembly dialect. The standard dialect is ATT, which is + assumed when this attribute is not present. When present, the dialect + is assumed to be Intel. Currently, ATT and Intel are the only supported + dialects.

inlinehint

This attribute indicates that the source code contained a hint that inlining this function is desirable (such as the "inline" keyword in C/C++). It @@ -1392,7 +1440,7 @@ target datalayout = "layout specification"

If no match is found, and the type sought is an integer type, then the smallest integer type that is larger than the bitwidth of the sought type is used. If none of the specifications are larger than the bitwidth then - the the largest integer type is used. For example, given the default + the largest integer type is used. For example, given the default specifications above, the i7 type will use the alignment of i8 (next largest) while both i65 and i256 will use the alignment of i64 (largest specified).

@@ -2287,8 +2335,9 @@ in signal handlers).

by 0xM followed by 32 hexadecimal digits. The IEEE 128-bit format is represented by 0xL followed by 32 hexadecimal digits; no currently supported target uses this format. Long doubles will only work if - they match the long double format on your target. All hexadecimal formats - are big-endian (sign bit at the left).

+ they match the long double format on your target. The IEEE 16-bit format + (half precision) is represented by 0xH followed by 4 hexadecimal + digits. All hexadecimal formats are big-endian (sign bit at the left).

There are no constants of type x86mmx.

@@ -2739,7 +2788,7 @@ second_end: make it fit in TYPE.

inttoptr (CST to TYPE)

Convert a integer constant to a pointer constant. TYPE must be a pointer +

Convert an integer constant to a pointer constant. TYPE must be a pointer type. CST must be of integer type. The CST value is zero extended, truncated, or unchanged to make it fit in a pointer size. This one is really dangerous!

@@ -2826,8 +2875,9 @@ i32 (i32) asm "bswap $0", "=r,r"

Inline assembler expressions may only be used as the callee operand of - a call instruction. Thus, typically we - have:

+ a call or an + invoke instruction. + Thus, typically we have:

 %X = call i32 asm "bswap $0", "=r,r"(i32 %Y)
@@ -3051,6 +3101,8 @@ call void @llvm.dbg.value(metadata !24, i64 0, metadata !25)
    The range should not represent the full or empty set. That is,
        a!=b. 
 
+ In addition, the pairs must be in signed order of the lower bound and
+  they must be non-contiguous.
 
 Examples:
 
@@ -3058,10 +3110,12 @@ call void @llvm.dbg.value(metadata !24, i64 0, metadata !25)
   %a = load i8* %x, align 1, !range !0 ; Can only be 0 or 1
   %b = load i8* %y, align 1, !range !1 ; Can only be 255 (-1), 0 or 1
   %c = load i8* %z, align 1, !range !2 ; Can only be 0, 1, 3, 4 or 5
+  %d = load i8* %z, align 1, !range !3 ; Can only be -2, -1, 3, 4 or 5
 ...
 !0 = metadata !{ i8 0, i8 2 }
 !1 = metadata !{ i8 255, i8 2 }
 !2 = metadata !{ i8 0, i8 2, i8 3, i8 6 }
+!3 = metadata !{ i8 -2, i8 0, i8 3, i8 6 }

@@ -4727,7 +4781,7 @@ IfUnequal:

Arguments:

The first two operands of a 'shufflevector' instruction are vectors - with types that match each other. The third argument is a shuffle mask whose + with the same type. The third argument is a shuffle mask whose element type is always 'i32'. The result of the instruction is a vector whose length is the same as the shuffle mask and whose element type is the same as the element type of the first two operands.

@@ -7464,6 +7518,74 @@ LLVM.

+ +

+ '`llvm.fabs.*`' Intrinsic +

+ +

Syntax:

This is an overloaded intrinsic. You can use llvm.fabs on any + floating point or vector of floating point type. Not all targets support all + types however.

+ +

+  declare float     @llvm.fabs.f32(float  %Val)
+  declare double    @llvm.fabs.f64(double %Val)
+  declare x86_fp80  @llvm.fabs.f80(x86_fp80  %Val)
+  declare fp128     @llvm.fabs.f128(fp128 %Val)
+  declare ppc_fp128 @llvm.fabs.ppcf128(ppc_fp128  %Val)
+

+ +

Overview:

The 'llvm.fabs.*' intrinsics return the absolute value of + the operand.

+ +

Arguments:

The argument and return value are floating point numbers of the same + type.

+ +

Semantics:

This function returns the same values as the libm fabs functions + would, and handles error conditions in the same way.

+ +

+ + +

+ '`llvm.floor.*`' Intrinsic +

+ +

Syntax:

This is an overloaded intrinsic. You can use llvm.floor on any + floating point or vector of floating point type. Not all targets support all + types however.

+ +

+  declare float     @llvm.floor.f32(float  %Val)
+  declare double    @llvm.floor.f64(double %Val)
+  declare x86_fp80  @llvm.floor.f80(x86_fp80  %Val)
+  declare fp128     @llvm.floor.f128(fp128 %Val)
+  declare ppc_fp128 @llvm.floor.ppcf128(ppc_fp128  %Val)
+

+ +

Overview:

The 'llvm.floor.*' intrinsics return the floor of + the operand.

+ +

Arguments:

The argument and return value are floating point numbers of the same + type.

+ +

Semantics:

This function returns the same values as the libm floor functions + would, and handles error conditions in the same way.

+ +

+ @@ -7940,12 +8062,59 @@ LLVM.

+ Specialised Arithmetic Intrinsics +

+ + + +

+ '`llvm.fmuladd.*`' Intrinsic +

+ +

Syntax:

+  declare float @llvm.fmuladd.f32(float %a, float %b, float %c)
+  declare double @llvm.fmuladd.f64(double %a, double %b, double %c)
+

+ +

Overview:

The 'llvm.fmuladd.*' intrinsic functions represent multiply-add +expressions that can be fused if the code generator determines that the fused +expression would be legal and efficient.

+ +

Arguments:

The 'llvm.fmuladd.*' intrinsics each take three arguments: two +multiplicands, a and b, and an addend c.

+ +

Semantics:

The expression:

+  %0 = call float @llvm.fmuladd.f32(%a, %b, %c)
+

is equivalent to the expression a * b + c, except that rounding will not be +performed between the multiplication and addition steps if the code generator +fuses the operations. Fusion is not guaranteed, even if the target platform +supports it. If a fused multiply-add is required the corresponding llvm.fma.* +intrinsic function should be used instead.

+ +

Examples:

+  %r2 = call float @llvm.fmuladd.f32(float %a, float %b, float %c) ; yields {float}:r2 = (a * b) + c
+

+ +

+ + +

Half Precision Floating Point Intrinsics

Half precision floating point is a storage-only format. This means that it is +

For most target platforms, 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 format.

@@ -8382,7 +8551,7 @@ LLVM.

Syntax:

-  declare void @llvm.trap()
+  declare void @llvm.trap() noreturn nounwind

Overview:

@@ -8392,9 +8561,33 @@ LLVM.

None.

Semantics:

This intrinsics is lowered to the target dependent trap instruction. If the +

This intrinsic 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.

+ a call of the abort() function.

+ +

+ + +

+ '`llvm.debugtrap`' Intrinsic +

+ +

Syntax:

+  declare void @llvm.debugtrap() nounwind
+

+ +

Overview:

The 'llvm.debugtrap' intrinsic.

+ +

Arguments:

None.

+ +

Semantics:

This intrinsic is lowered to code which is intended to cause an execution + trap with the intention of requesting the attention of a debugger.

@@ -8441,8 +8634,8 @@ LLVM.

Syntax:

-  declare i32 @llvm.objectsize.i32(i8* <object>, i1 <type>)
-  declare i64 @llvm.objectsize.i64(i8* <object>, i1 <type>)
+  declare i32 @llvm.objectsize.i32(i8* <object>, i1 <min>)
+  declare i64 @llvm.objectsize.i64(i8* <object>, i1 <min>)

Overview:

@@ -8455,15 +8648,15 @@ LLVM.

Arguments:

The llvm.objectsize intrinsic takes two arguments. The first argument is a pointer to or into the object. The second argument - is a boolean 0 or 1. This argument determines whether you want the - maximum (0) or minimum (1) bytes remaining. This needs to be a literal 0 or - 1, variables are not allowed.

+ is a boolean and determines whether llvm.objectsize returns 0 (if + true) or -1 (if false) when the object size is unknown. + The second argument only accepts constants.

Semantics:

The llvm.objectsize intrinsic is lowered to either a constant - representing the size of the object concerned, or i32/i64 -1 or 0, - depending on the type argument, if the size cannot be determined at - compile time.

The llvm.objectsize intrinsic is lowered to a constant representing + the size of the object concerned. If the size cannot be determined at compile + time, llvm.objectsize returns i32/i64 -1 or 0 + (depending on the min argument).

@@ -8492,6 +8685,30 @@ LLVM.

This intrinsic is lowered to the val.

+ +

+ '`llvm.donothing`' Intrinsic +

+ +

Syntax:

+  declare void @llvm.donothing() nounwind readnone
+

+ +

Overview:

The llvm.donothing intrinsic doesn't perform any operation. It's the +only intrinsic that can be called with an invoke instruction.

+ +

Arguments:

None.

+ +

Semantics:

This intrinsic does nothing, and it's removed by optimizers and ignored by +codegen.

+ @@ -8505,7 +8722,7 @@ LLVM.

Chris Lattner
The LLVM Compiler Infrastructure
- Last modified: $Date: 2012-04-16 21:39:33 +0200 (Mon, 16 Apr 2012) $ + Last modified: $Date: 2012-08-10 02:00:22 +0200 (Fri, 10 Aug 2012) $ -- cgit v1.1

Arguments:

+ 'llvm.fabs.*' Intrinsic +

Syntax:

Overview:

Arguments:

Semantics:

+ 'llvm.floor.*' Intrinsic +

Syntax:

Overview:

Arguments:

Semantics:

+ Specialised Arithmetic Intrinsics +

+ 'llvm.fmuladd.*' Intrinsic +

Syntax:

Overview:

Arguments:

Semantics:

Examples:

Half Precision Floating Point Intrinsics

Syntax:

Overview:

Semantics:

+ 'llvm.debugtrap' Intrinsic +

Syntax:

Overview:

Arguments:

Semantics:

Syntax:

Overview:

Arguments:

Semantics:

+ 'llvm.donothing' Intrinsic +

Syntax:

Overview:

Arguments:

Semantics:

+ '`llvm.fabs.*`' Intrinsic +

+ '`llvm.floor.*`' Intrinsic +

+ '`llvm.fmuladd.*`' Intrinsic +

+ '`llvm.debugtrap`' Intrinsic +

+ '`llvm.donothing`' Intrinsic +