Displaying 3 results from an estimated 3 matches for "computedeadvalues".
2017 Jun 27
4
Ok with mismatch between dead-markings in BUNDLE and bundled instructions?
...the register allocator later tries to spill/reload %vreg39 it
thinks that %vreg39 is live, so it inserts a reload after the bundle,
but then the verifier pukes on it and says that there is a use of the
register after it's dead.
The dead-marking on the BUNDLE is introduced by
LiveIntervals::computeDeadValues which does
// This is a dead def. Make sure the instruction knows.
MachineInstr *MI = getInstructionFromIndex(Def);
assert(MI && "No instruction defining live value");
MI->addRegisterDead(LI.reg, TRI);
and the reload after the BUNDLE is introduced...
2017 Jun 27
5
Ok with mismatch between dead-markings in BUNDLE and bundled instructions?
...llocator later tries to spill/reload %vreg39 it thinks that %vreg39 is live, so it inserts a reload after the bundle, but then the verifier pukes on it and says that there is a use of the register after it's dead.
>>
>> The dead-marking on the BUNDLE is introduced by LiveIntervals::computeDeadValues which does
>>
>> // This is a dead def. Make sure the instruction knows.
>> MachineInstr *MI = getInstructionFromIndex(Def);
>> assert(MI && "No instruction defining live value");
>> MI->addRegisterDead(LI.reg, TRI);
>
> I t...
2015 Apr 20
2
[LLVMdev] Multiple connected components in live interval
Hi Jonas,
> On Apr 20, 2015, at 4:03 AM, Jonas Paulsson <jonas.paulsson at ericsson.com> wrote:
>
> Hi Quentin,
>
> After Simple Register Coalescing.
Is the code you have pasted with the PHIs feed to the register coalescer?
I am trying to understand the setting to help debugging the problem.
Also, what does -debug-only=regalloc tell you?
Thanks,
-Quentin
>
>