Displaying 2 results from an estimated 2 matches for "delayslotdescriptor".
2018 Oct 01
2
OptBisect implementation for new pass manager
On 10/01/2018 08:39 PM, David Greene wrote:
> "Kaylor, Andrew" <andrew.kaylor at intel.com> writes:
>
>> What if in the registration interface we had three options: skippable,
>> not skippable, and run at OptLevel::None.
> I kind of like this idea. If necessary, the pass could even query the
> target (or some other entity) about what OptLevel::None means.
2018 Oct 01
2
OptBisect implementation for new pass manager
...n, TTI may or may not be the right place to put such a query
> interface, but it seems in-line with the role TTI plays.
>
> Again, this isn't something that needs to be solved right now, but in
> my head the model looks something like this:
>
> MySchedulingPass::run() {
> DelaySlotDescriptor = TM.getDelaySlotInfo();
> InterlockDescriptor = TM.getSoftwareInterlocks();
> VLIWDescriptor = TM.getBundleInfo();
>
> if (PassInstrumentor.getOptLevel() == OptLevel::None) {
> // Schedule only for the above constraints (e.g. fill all delay slots
> // with nops, ide...