Displaying 14 results from an estimated 14 matches for "reg_nodbg_empty".
2011 Feb 22
1
[LLVMdev] virtual register does not exist
Hi
is there a way to know later that an earlier pass inside the codegen
might have eliminated a virtual register.
I carry information abt virtual registers which i would like to update
if any virtual register does not exist since.
thanks
dz
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...gister 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(TargetReg...
2016 May 25
0
[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 !...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...? 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();...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...ome 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
>> =...
2016 May 24
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...; a correct way to 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:
> >...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...rrect way to 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.
> 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++ ) {
&g...
2016 May 25
3
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...y to 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.
>> 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...
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_b...
2016 May 25
2
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...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...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...t;>>>>
>>>>> 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...
2016 May 25
0
[GSoC 2016] Interprocedural Register Allocation - Introduction and Feedback
...> > > > > > > > > > UsedPhysRegMask.test(PhysReg)
> > > > > > > > > > is
> > > > > > > > > > true
> > > > > > > > > > or
> > > > > > > > > > because reg_nodbg_empty(*AliasReg) is true.
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
> > > > > > > > >...
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 : " <<
2011 Feb 23
0
[LLVMdev] LLVMdev Digest, Vol 80, Issue 37-Help to unsubscribe
...here a way to know later that an earlier pass inside the codegen
> might have eliminated a virtual register.
> I carry information abt virtual registers which i would like to update
> if any virtual register does not exist since.
You can check if any instructions are using it with MRI->reg_nodbg_empty(Reg).
/jakob
------------------------------
Message: 22
Date: Tue, 22 Feb 2011 19:46:24 -0500
From: F?lix Cloutier <felixcca at yahoo.ca>
Subject: Re: [LLVMdev] Can I use Clang to parse snippets of C++ code?
To: Chris Lattner <clattner at apple.com>
Cc: LLVM Developers Mailing Lis...