Displaying 4 results from an estimated 4 matches for "getregisterpressurelimit".
2011 Oct 26
1
[LLVMdev] [llvm-commits] Bottom-Up Scheduling?
...ture is probably to make it work as much like ARM as possible.
This means (1) defaulting to the "hybrid" scheduler, (2) implementing the
register pressure limit, and (3) reenabling the hazard recognizer.
(1) TargetLowering::setSchedulingPreference(Sched::Hybrid)
(2) TargetRegisterInfo::getRegisterPressureLimit(...) should probably
return something a bit less than 32, depending on register class.
(3) The standard hazard recognizer works either bottom-up or top-down
on the itinerary data. So it *should* work out-of-box. The problem is
that PPC has overriden the API to layer some custom "bundling"...
2011 Nov 22
0
[LLVMdev] [llvm-commits] Bottom-Up Scheduling?
...much like ARM as possible.
>
> This means (1) defaulting to the "hybrid" scheduler, (2) implementing the
> register pressure limit, and (3) reenabling the hazard recognizer.
>
> (1) TargetLowering::setSchedulingPreference(Sched::Hybrid)
>
> (2) TargetRegisterInfo::getRegisterPressureLimit(...) should probably
> return something a bit less than 32, depending on register class.
>
> (3) The standard hazard recognizer works either bottom-up or top-down
> on the itinerary data. So it *should* work out-of-box. The problem is
> that PPC has overriden the API to layer some c...
2011 Oct 26
3
[LLVMdev] Bottom-Up Scheduling?
Is there documentation somewhere for the bottom-up scheduling? I'm
trying to figure out what changes are necessary in order to support it
in the PPC backend.
Thanks in advance,
Hal
On Thu, 2011-10-20 at 10:21 -0700, Evan Cheng wrote:
>
> On Oct 19, 2011, at 7:29 PM, Hal Finkel <hfinkel at anl.gov> wrote:
>
> > Evan,
> >
> > Thanks for the heads up! Is
2011 Nov 28
2
[LLVMdev] [llvm-commits] Bottom-Up Scheduling?
...t;
> > This means (1) defaulting to the "hybrid" scheduler, (2) implementing the
> > register pressure limit, and (3) reenabling the hazard recognizer.
> >
> > (1) TargetLowering::setSchedulingPreference(Sched::Hybrid)
> >
> > (2) TargetRegisterInfo::getRegisterPressureLimit(...) should probably
> > return something a bit less than 32, depending on register class.
> >
> > (3) The standard hazard recognizer works either bottom-up or top-down
> > on the itinerary data. So it *should* work out-of-box. The problem is
> > that PPC has override...