Displaying 14 results from an estimated 14 matches for "tempreg".
Did you mean:
temp_reg
2005 Jul 25
1
[LLVMdev] How to partition registers into different RegisterClass?
...> allocation_order_end()).
>
> -Chris
Hope I understand you correctly:
def C0 : ConstFpReg<0, "c0">;
...
def C200 : ConstFpReg<199, "c200">;
def I0 : ConstIntReg<0, "i0">;
...
def I100 : ConstIntReg<100, "i100">;
def R0 : TempReg<0, "r0">;
def R32 : TempReg<31, "r32">;
def V0 : InputReg<0, "v0">;
..
def V10 : InputReg<9, "v10">;
def O0 : OutputReg<0, "o0">;
..
def O4 : OutputReg<4, "o4">;
def FloatingPointRC : RegisterClass<...
2005 Jul 23
0
[LLVMdev] How to partition registers into different RegisterClass?
On Sat, 23 Jul 2005, Tzu-Chien Chiu wrote:
> 2005/7/23, Chris Lattner <sabre at nondot.org>:
>> What does a 'read only' register mean? Is it a constant (e.g. returns
>> 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
2005 Jul 23
3
[LLVMdev] How to partition registers into different RegisterClass?
2005/7/23, Chris Lattner <sabre at nondot.org>:
>
> What does a 'read only' register mean? Is it a constant (e.g. returns
> 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
2008 Nov 17
2
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
..., I can not find any llvm::MVT::SimpleValueType which can represents
a 96-bit register.
Thus, my question is:
1) Does current LLVM backend supports this H/W?
2) If yes, how can I write the type of the register class in my .td file?
(Which value should I fill in the following 'XXX' ?)
def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3, R4, R5,
R6, R7, R8, R9,
R10, R11, R12, R13, R14,
R15, R16, R17, R18, R19,
R20, R21, R22, R23, R24,
R25, R26, R27, R28, R29,...
2008 Nov 20
4
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
...bit register.
>
> > Thus, my question is:
>
> > 1) Does current LLVM backend supports this H/W?
> > 2) If yes, how can I write the type of the register class in my .td
> > file?
>
> > (Which value should I fill in the following 'XXX' ?)
> > def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3,
> > R4, R5, R6, R7, R8, R9,
> > R10, R11, R12,
> > R13, R14, R15, R16, R17, R18, R19,
> > R20, R21, R...
2008 Nov 18
0
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
...ch can
> represents a 96-bit register.
>
> Thus, my question is:
>
> 1) Does current LLVM backend supports this H/W?
> 2) If yes, how can I write the type of the register class in my .td
> file?
>
> (Which value should I fill in the following 'XXX' ?)
> def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3,
> R4, R5, R6, R7, R8, R9,
> R10, R11, R12,
> R13, R14, R15, R16, R17, R18, R19,
> R20, R21, R22,
> R23, R24,...
2014 Jun 08
2
[LLVMdev] [llvm] r210424 - Revert "Do materialize for floating point"
...astISel::MaterializeFP(const ConstantFP *CFP, MVT VT) {
> - int64_t Imm = CFP->getValueAPF().bitcastToAPInt().getZExtValue();
> - if (VT == MVT::f32) {
> - const TargetRegisterClass *RC = &Mips::FGR32RegClass;
> - unsigned DestReg = createResultReg(RC);
> - unsigned TempReg = Materialize32BitInt(Imm, &Mips::GPR32RegClass);
> - EmitInst(Mips::MTC1, DestReg).addReg(TempReg);
> - return DestReg;
> - } else if (VT == MVT::f64) {
> - const TargetRegisterClass *RC = &Mips::AFGR64RegClass;
> - unsigned DestReg = createResultReg(RC);
> -...
2008 Nov 21
0
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
...gt;> Thus, my question is:
>>
>>> 1) Does current LLVM backend supports this H/W?
>>> 2) If yes, how can I write the type of the register class in my .td
>>> file?
>>
>>> (Which value should I fill in the following 'XXX' ?)
>>> def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3,
>>> R4, R5, R6, R7, R8, R9,
>>> R10, R11, R12,
>>> R13, R14, R15, R16, R17, R18, R19,
>>> R20...
2008 Nov 20
0
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
...gt;> Thus, my question is:
>>
>>> 1) Does current LLVM backend supports this H/W?
>>> 2) If yes, how can I write the type of the register class in my .td
>>> file?
>>
>>> (Which value should I fill in the following 'XXX' ?)
>>> def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3,
>>> R4, R5, R6, R7, R8, R9,
>>> R10, R11, R12,
>>> R13, R14, R15, R16, R17, R18, R19,
>>> R20...
2008 Nov 22
2
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
...question is:
>
> >>> 1) Does current LLVM backend supports this H/W?
> >>> 2) If yes, how can I write the type of the register class in my .td
> >>> file?
>
> >>> (Which value should I fill in the following 'XXX' ?)
> >>> def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3,
> >>> R4, R5, R6, R7, R8, R9,
> >>> R10, R11, R12,
> >>> R13, R14, R15, R16, R17, R18, R19,
> >>> ...
2008 Nov 24
0
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
...Does current LLVM backend supports this H/W?
>>>>> 2) If yes, how can I write the type of the register class in
>>>>> my .td
>>>>> file?
>>
>>>>> (Which value should I fill in the following 'XXX' ?)
>>>>> def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3,
>>>>> R4, R5, R6, R7, R8, R9,
>>>>> R10, R11, R12,
>>>>> R13, R14, R15, R16, R17, R18, R19,
>>>>>...
2008 Nov 22
2
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
...question is:
>
> >>> 1) Does current LLVM backend supports this H/W?
> >>> 2) If yes, how can I write the type of the register class in my .td
> >>> file?
>
> >>> (Which value should I fill in the following 'XXX' ?)
> >>> def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3,
> >>> R4, R5, R6, R7, R8, R9,
> >>> R10, R11, R12,
> >>> R13, R14, R15, R16, R17, R18, R19,
> >>> ...
2008 Nov 22
0
[LLVMdev] Does current LLVM target-independent code generator supports my strange chip?
...Does current LLVM backend supports this H/W?
>>>>> 2) If yes, how can I write the type of the register class in
>>>>> my .td
>>>>> file?
>>
>>>>> (Which value should I fill in the following 'XXX' ?)
>>>>> def TempRegs : RegisterClass<"MFLEXG", [XXX], 32, [R0, R1, R2, R3,
>>>>> R4, R5, R6, R7, R8, R9,
>>>>> R10, R11, R12,
>>>>> R13, R14, R15, R16, R17, R18, R19,
>>>>>...
2009 May 22
0
Wine release 1.1.22
..._add_dst_param and make it shader_arb_get_dst_param.
wined3d: Simplify shader_hw_map2gl.
wined3d: Tidy up shader_hw_rsq_rcp.
wined3d: Standardize pshader_hw_texkill.
wined3d: Tidy up pshader_hw_tex.
wined3d: Fix 1.4 pshader projection in ARB.
wined3d: Separate Tx tempregs from Tx varyings in ARB.
wined3d: Tidy up pshader_hw_cnd.
wined3d: Tidy up pshader_hw_cmp.
wined3d: Tidy up pshader_hw_dp2add.
wined3d: Tidy up pshader_hw_texreg2rgb and friends.
wined3d: Fix a few more hardcoded pixel shader registers.
wined3d: Fix remaining in...