Displaying 8 results from an estimated 8 matches for "vector4".
Did you mean:
vector
2005 Jul 23
3
[LLVMdev] How to partition registers into different RegisterClass?
...s
> 1.0)? Otherwise, how can it be a useful value?
Yes, it's a constant register.
Because the instruction cannot contain an immediate value, a constant
value may be stored in a constant register, and it's defined _before_
the program starts by API. For example:
SetConstantValue( 5, Vector4( 1, 2, 3, 4 ); // C5 = <1,2,3,4>
HANDLE handle = LoadCodeFromFile( filename );
SetCode( handle ); // C5 is referenced here
Execute();
--
Tzu-Chien Chiu,
3D Graphics Hardware Enginner,
<URL:http://www.csie.nctu.edu.tw/~jwchiu>
2008 Jun 13
1
x86 SSE* Pointer Favors
...of my code, or are
there specific libraries that I should call?
What I want to learn about is as simple as it gets:
typedef double Double; // or whatever SSE* needs as close equivalent
Double vector1[N], vector2[N];
// then fill them with stuff.
vector3= vector_mult(vector1,vector2, N);
vector4= sum(vector1, N);
I just need a pointer and/or primer. PS: If someone knows of a
superfast vectorized implementation of Gentleman's WLS algorithm,
please point me to it, too. I am still using my old non-vectorized C
routines.
if this email offends as spam, apologies.
regards,
/iaw
2005 Jul 23
0
[LLVMdev] How to partition registers into different RegisterClass?
...be a useful value?
>
> Yes, it's a constant register.
>
> Because the instruction cannot contain an immediate value, a constant
> value may be stored in a constant register, and it's defined _before_
> the program starts by API. For example:
>
> SetConstantValue( 5, Vector4( 1, 2, 3, 4 ); // C5 = <1,2,3,4>
> HANDLE handle = LoadCodeFromFile( filename );
> SetCode( handle ); // C5 is referenced here
> Execute();
Ah, ok. In that case, you want to put all of the registers in one register
file, and not make the constant register allocatable (e.g. see...
2005 Jul 25
2
[LLVMdev] How to partition registers into different RegisterClass?
...es, it's a constant register.
> >
> > Because the instruction cannot contain an immediate value, a constant
> > value may be stored in a constant register, and it's defined _before_
> > the program starts by API. For example:
> >
> > SetConstantValue( 5, Vector4( 1, 2, 3, 4 ); // C5 = <1,2,3,4>
> > HANDLE handle = LoadCodeFromFile( filename );
> > SetCode( handle ); // C5 is referenced here
> > Execute();
>
> Ah, ok. In that case, you want to put all of the registers in one register
> file, and not make the constant re...
2005 Jul 22
0
[LLVMdev] How to partition registers into different RegisterClass?
On Fri, 22 Jul 2005, Tzu-Chien Chiu wrote:
> All registers in my hardware are 4-element vector registers (128-bit).
> Some are floating point registers, and the others are integer
> registers.
>
> I typedef two packed classes: [4 x float] and [4 x int], and add an
> enum 'packed' to MVT::ValueType (ValuesTypes.h).
>
> I declared all 'RegisterClass'es to be
2005 Jul 22
2
[LLVMdev] How to partition registers into different RegisterClass?
All registers in my hardware are 4-element vector registers (128-bit).
Some are floating point registers, and the others are integer
registers.
I typedef two packed classes: [4 x float] and [4 x int], and add an
enum 'packed' to MVT::ValueType (ValuesTypes.h).
I declared all 'RegisterClass'es to be 'packed' (first argument of
RegisterClass):
def GeneralPurposeRC :
2005 Jul 26
0
[LLVMdev] How to partition registers into different RegisterClass?
...stant register.
>>>
>>> Because the instruction cannot contain an immediate value, a constant
>>> value may be stored in a constant register, and it's defined _before_
>>> the program starts by API. For example:
>>>
>>> SetConstantValue( 5, Vector4( 1, 2, 3, 4 ); // C5 = <1,2,3,4>
>>> HANDLE handle = LoadCodeFromFile( filename );
>>> SetCode( handle ); // C5 is referenced here
>>> Execute();
>>
>> Ah, ok. In that case, you want to put all of the registers in one register
>> file, and not...
2000 Nov 15
8
Optimisations
Looking through the archives I have seen talk of making CPU specific
optimisations for Vorbis, a la MMX/3DNow!/SSE. The feeling I gather is to
wait until something is working well in C before committing to any kind of
specific optimisation. What if oft used and needed DSP functions were
identified and standardised DSP functionality be written for Vorbis? This
would seperate the basically