Displaying 5 results from an estimated 5 matches for "instructionitinerari".
Did you mean:
instructionitinerary
2012 May 11
0
[LLVMdev] Scheduler Roadmap
On May 9, 2012, at 8:34 AM, dag at cray.com wrote:
> Andrew Trick <atrick at apple.com> writes:
>
>>> When I asked about enhancing scheduler heuristics a month or so ago, I
>>> got a response about a MachineInstr scheduler and that that was the way
>>> of the LLVM future. Is that so? Is the ScheduleDAG going away?
>>
>> You sent a lengthy RFC
2012 May 11
2
[LLVMdev] Scheduler Roadmap
On Thu, 10 May 2012 20:33:53 -0700
Andrew Trick <atrick at apple.com> wrote:
> On May 9, 2012, at 8:34 AM, dag at cray.com wrote:
>
> > Andrew Trick <atrick at apple.com> writes:
> >
> >>> When I asked about enhancing scheduler heuristics a month or so
> >>> ago, I got a response about a MachineInstr scheduler and that
> >>> that
2012 May 11
0
[LLVMdev] Scheduler Roadmap
On May 10, 2012, at 9:06 PM, Hal Finkel <hfinkel at anl.gov> wrote:
>> - Target pass configuration: DONE
>> - MachineScheduler pass framework: DONE
>> - MI Scheduling DAG: DONE
>> - AliasAnalysis aware DAG option: In review (Sergei)
>> - Bidirectional list scheduling: DONE
>> - LiveInterval Update: WIP (simple instruction reordering is
>> supported)
2012 May 09
5
[LLVMdev] Scheduler Roadmap
Andrew Trick <atrick at apple.com> writes:
>> When I asked about enhancing scheduler heuristics a month or so ago, I
>> got a response about a MachineInstr scheduler and that that was the way
>> of the LLVM future. Is that so? Is the ScheduleDAG going away?
>
> You sent a lengthy RFC on Apr 20 that demonstrated you aren't
> following developments on trunk.
2012 May 11
3
[LLVMdev] Scheduler Roadmap
My 2c...
Even though I understand it might be way off in the future, but we are
talking about long term plans here anyway. Also as a VLIW backend
maintainer, I just have to say it :)
- We do need to have a way to assign bundles much earlier than we do now.
And it needs to be intertwined with scheduling (Bundler currently reuses a
good chunk of scheduler infrastructure). It is also obvious