Displaying 3 results from an estimated 3 matches for "getphysicalregistervt".
2016 Jul 29
2
Understanding failed assert in reg pressure reduction list scheduler
...not entirely certain what the
correct behaviour is.
My rough understanding of the problem is that, while attempting to pick a
node to schedule, we're running out of candidates (in
ScheduleDAGRRList::PickNodeToScheduleBottomUp). This causes us to try to
copy a node, and in the process, we call getPhysicalRegisterVT. This
function asserts that the MCInstrDesc associated with the node will have
ImplicitDefs, but in our case, it does not.
In short: does this seem to be a problem of missing information in the
MCInstrDesc, or should we not have arrived at that assert in the first
place?
Thanks,
- Elliot
-------...
2016 Jul 29
0
Understanding failed assert in reg pressure reduction list scheduler
...at the correct behaviour is.
>
> My rough understanding of the problem is that, while attempting to pick
> a node to schedule, we're running out of candidates (in
> ScheduleDAGRRList::PickNodeToScheduleBottomUp). This causes us to try to
> copy a node, and in the process, we call getPhysicalRegisterVT. This
> function asserts that the MCInstrDesc associated with the node will have
> ImplicitDefs, but in our case, it does not.
>
> In short: does this seem to be a problem of missing information in the
> MCInstrDesc, or should we not have arrived at that assert in the first
> plac...
2016 Jul 29
1
Understanding failed assert in reg pressure reduction list scheduler
...is.
> >
> > My rough understanding of the problem is that, while attempting to pick
> > a node to schedule, we're running out of candidates (in
> > ScheduleDAGRRList::PickNodeToScheduleBottomUp). This causes us to try
to
> > copy a node, and in the process, we call getPhysicalRegisterVT. This
> > function asserts that the MCInstrDesc associated with the node will
have
> > ImplicitDefs, but in our case, it does not.
> >
> > In short: does this seem to be a problem of missing information in the
> > MCInstrDesc, or should we not have arrived at that asse...