Displaying 7 results from an estimated 7 matches for "add_sat".
2005 Jul 27
3
[LLVMdev] How to define complicated instruction in TableGen (Direct3D shader instruction)
Each register is a 4-component (namely, r, g, b, a) vector register.
They are actually defined as llvm packed [4xfloat].
The instruction:
add_sat r0.a, r1_bias.xxyy, r3_x2.zzzz
Explaination:
'.a' is a writemask. only the specified component will be update
'.xxyy' and '.zzzz' are swizzle masks, specify the component
permutation, simliar to the Intel SSE permutation instruction SHUFPD
'_bias' and '_x2...
2005 Jul 29
0
[LLVMdev] How to define complicated instruction in TableGen (Direct3D shader instruction)
...ttern instruction selector to
recognise the shuffle+add combination and emit a single instruction.
m.
Tzu-Chien Chiu wrote:
> Each register is a 4-component (namely, r, g, b, a) vector register.
> They are actually defined as llvm packed [4xfloat].
>
> The instruction:
>
> add_sat r0.a, r1_bias.xxyy, r3_x2.zzzz
>
> Explaination:
>
> '.a' is a writemask. only the specified component will be update
>
> '.xxyy' and '.zzzz' are swizzle masks, specify the component
> permutation, simliar to the Intel SSE permutation instruction SHUF...
2005 Aug 31
2
[LLVMdev] Anyone is building a DSP-C frontend?
...0r !!! */
this qualifier can be implemented just like the 'const' qualifier.
btw, in some implementation, the saturation is explicitly specifiedby
the arithmetic operation, not the variable itself. for example:
/* add the operands, saturate the result before it's assigned to c */
c = add_sat(-0.75, -0.75);
2. memory space qualifier
a typical program will have its global variables and constant in
different data segments. a segment is just a block with continuous
memory. there is no difference where the segment is. however, it's
different in the embedded system. usually constants a...
2005 Aug 31
0
[LLVMdev] Anyone is building a DSP-C frontend?
...t; a = -0.75r; // 'r' is fixed-point number postfix
> b = -0.75r;
> c = a + b; /* c = -1.0r !!! */
>
> this qualifier can be implemented just like the 'const' qualifier.
This shouldn't be a type qualifier, if implemented in llvm, this should be
new operations (e.g. add_sat). Saturating arithmetic would also be
interesting for the vector/simd people.
> btw, in some implementation, the saturation is explicitly specifiedby
> the arithmetic operation, not the variable itself. for example:
>
> /* add the operands, saturate the result before it's assigne...
2016 Apr 08
2
LIBCLC with LLVM 3.9 Trunk
It's not clear what is actually wrong from your original message, I think
you need to give some more information as to what you are doing: Example
source, what target GPU, compiler error messages or other evidence of "it's
wrong" (llvm IR, disassembly, etc) ...
--
Mats
On 8 April 2016 at 09:55, Liu Xin via llvm-dev <llvm-dev at lists.llvm.org>
wrote:
> I built it
2011 Dec 13
0
[LLVMdev] Changes to the PTX calling conventions
On Tue, Dec 13, 2011 at 3:37 PM, Villmow, Micah <Micah.Villmow at amd.com>wrote:
> ** **
>
> *From:* Justin Holewinski [mailto:justin.holewinski at gmail.com]
> *Sent:* Tuesday, December 13, 2011 10:50 AM
>
> *To:* Villmow, Micah
> *Cc:* LLVM Developers Mailing List
> *Subject:* Re: [LLVMdev] Changes to the PTX calling conventions****
>
> ** **
>
> On
2011 Dec 13
3
[LLVMdev] Changes to the PTX calling conventions
From: Justin Holewinski [mailto:justin.holewinski at gmail.com]
Sent: Tuesday, December 13, 2011 10:50 AM
To: Villmow, Micah
Cc: LLVM Developers Mailing List
Subject: Re: [LLVMdev] Changes to the PTX calling conventions
On Tue, Dec 13, 2011 at 12:54 PM, Villmow, Micah <Micah.Villmow at amd.com<mailto:Micah.Villmow at amd.com>> wrote:
From: Justin Holewinski [mailto:justin.holewinski