Displaying 14 results from an estimated 14 matches for "aliasreg".
Did you mean:
aliases
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...rmation ? I think I have made some mistake please help.
>
>
> You might look at the implementation of these functions in
> lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning
> true because UsedPhysRegMask.test(PhysReg) is true or because
> reg_nodbg_empty(*AliasReg) is true.
>
Yes that helped now I am getting actual register which have been used by
given function, but a little problem
The updated code is as shown below :
for(TargetRegisterInfo::regclass_iterator i = (*TRI).regclass_begin(), e =
(*TRI).regclass_end(); i != e; i++ ) {
for(TargetRegisterClass...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...de some mistake please help.
> >
>
> > You might look at the implementation of these functions in
> > lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're
> > returning true because UsedPhysRegMask.test(PhysReg) is true or
> > because reg_nodbg_empty(*AliasReg) is true.
>
> Yes that helped now I am getting actual register which have been used
> by given function, but a little problem
> The updated code is as shown below :
> for(TargetRegisterInfo::regclass_iterator i =
> (*TRI).regclass_begin(), e = (*TRI).regclass_end(); i != e; i++ )...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...made some mistake please help.
>>
>>
>> You might look at the implementation of these functions in
>> lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning
>> true because UsedPhysRegMask.test(PhysReg) is true or because
>> reg_nodbg_empty(*AliasReg) is true.
>>
> Yes that helped now I am getting actual register which have been used by
> given function, but a little problem
> The updated code is as shown below :
> for(TargetRegisterInfo::regclass_iterator i = (*TRI).regclass_begin(), e =
> (*TRI).regclass_end(); i != e; i+...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...e help.
>>>
>>>
>>> You might look at the implementation of these functions in
>>> lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning
>>> true because UsedPhysRegMask.test(PhysReg) is true or because
>>> reg_nodbg_empty(*AliasReg) is true.
>>>
>> Yes that helped now I am getting actual register which have been used by
>> given function, but a little problem
>> The updated code is as shown below :
>> for(TargetRegisterInfo::regclass_iterator i = (*TRI).regclass_begin(), e
>> = (*TRI).re...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...register usage information ? I think I have made some mistake please help.
>
> You might look at the implementation of these functions in lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning true because UsedPhysRegMask.test(PhysReg) is true or because reg_nodbg_empty(*AliasReg) is true.
> Yes that helped now I am getting actual register which have been used by given function, but a little problem
> The updated code is as shown below :
> for(TargetRegisterInfo::regclass_iterator i = (*TRI).regclass_begin(), e = (*TRI).regclass_end(); i != e; i++ ) {
> for(T...
2016 May 25
3
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...usage information ? I think I have made some mistake please help.
>>
>> You might look at the implementation of these functions in lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning true because UsedPhysRegMask.test(PhysReg) is true or because reg_nodbg_empty(*AliasReg) is true.
>> Yes that helped now I am getting actual register which have been used by given function, but a little problem
>> The updated code is as shown below :
>> for(TargetRegisterInfo::regclass_iterator i = (*TRI).regclass_begin(), e = (*TRI).regclass_end(); i != e; i++ ) {...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...>>>>
>>>> You might look at the implementation of these functions in
>>>> lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning
>>>> true because UsedPhysRegMask.test(PhysReg) is true or because
>>>> reg_nodbg_empty(*AliasReg) is true.
>>>>
>>> Yes that helped now I am getting actual register which have been used by
>>> given function, but a little problem
>>> The updated code is as shown below :
>>> for(TargetRegisterInfo::regclass_iterator i = (*TRI).regclass_begin(), e...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...stake please help.
>>>>>>>>
>>>>>>>> You might look at the implementation of these functions in lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning true because UsedPhysRegMask.test(PhysReg) is true or because reg_nodbg_empty(*AliasReg) is true.
>>>>>>> Yes that helped now I am getting actual register which have been used by given function, but a little problem
>>>>>>> The updated code is as shown below :
>>>>>>> for(TargetRegisterInfo::regclass_iterator i = (*TRI).r...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...;
>>>>> You might look at the implementation of these functions in
>>>>> lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning
>>>>> true because UsedPhysRegMask.test(PhysReg) is true or because
>>>>> reg_nodbg_empty(*AliasReg) is true.
>>>>>
>>>> Yes that helped now I am getting actual register which have been used
>>>> by given function, but a little problem
>>>> The updated code is as shown below :
>>>> for(TargetRegisterInfo::regclass_iterator i = (*TRI)....
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...gt; > > > > > > UsedPhysRegMask.test(PhysReg)
> > > > > > > > > > is
> > > > > > > > > > true
> > > > > > > > > > or
> > > > > > > > > > because reg_nodbg_empty(*AliasReg) is true.
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
> > > > > > > > > Yes that h...
2016 May 24
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...o get register usage information ? I think I have
> made some mistake please help.
You might look at the implementation of these functions in lib/CodeGen/MachineRegisterInfo.cpp and figure out if they're returning true because UsedPhysRegMask.test(PhysReg) is true or because reg_nodbg_empty(*AliasReg) is true.
-Hal
> Vivek
> On Wed, May 18, 2016 at 11:42 PM, Quentin Colombet <
> qcolombet at apple.com > wrote:
> > > On May 18, 2016, at 11:00 AM, vivek pandya <
> > > vivekvpandya at gmail.com
> > > >
> > > wrote:
> >
>
&g...
2016 May 24
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
Hello,
I have written following code to check each register if it is used by
machineFunction or not :
MachineRegisterInfo *MRI = &MF.getRegInfo();
TargetRegisterInfo *TRI = (TargetRegisterInfo
*)MF.getSubtarget().getRegisterInfo();
const TargetMachine &TM = MF.getTarget();
const MCRegisterInfo *MCRI = TM.getMCRegisterInfo();
DEBUG(dbgs() << "Function Name : " <<
2013 Apr 01
0
[LLVMdev] proposed change to class BasicTTI and dual mode mips16/32 working
...Node *N, unsigned Opc, DebugLoc DL, EVT Ty,
diff --git a/lib/Target/Mips/Mips16ISelDAGToDAG.h b/lib/Target/Mips/Mips16ISelDAGToDAG.h
index baa8587..f05f9b7 100644
--- a/lib/Target/Mips/Mips16ISelDAGToDAG.h
+++ b/lib/Target/Mips/Mips16ISelDAGToDAG.h
@@ -28,6 +28,8 @@ private:
SDValue getMips16SPAliasReg();
+ virtual bool runOnMachineFunction(MachineFunction &MF);
+
void getMips16SPRefReg(SDNode *Parent, SDValue &AliasReg);
virtual bool selectAddr16(SDNode *Parent, SDValue N, SDValue &Base,
diff --git a/lib/Target/Mips/MipsAsmPrinter.cpp b/lib/Target/Mips/MipsAsmPrinter.cpp
i...
2013 Apr 01
3
[LLVMdev] proposed change to class BasicTTI and dual mode mips16/32 working
On Thu, Mar 28, 2013 at 12:22 PM, Nadav Rotem <nrotem at apple.com> wrote:
> IMHO the right way to handle target function attributes is to
> re-initialize the target machine and TTI for every function (if the
> attributes changed). Do you have another solution in mind ?
I don't really understand this.
TargetMachine and TTI may be quite expensive to initialize. Doing so for