search for: hazardchecker

...i) >> - Bidirectional list scheduling: DONE >> - LiveInterval Update: WIP (simple instruction reordering is >> supported) >> - Target-independent precise modeling of register pressure: DONE >> - Register pressure reduction scheduler: WIP >> - Support for existing HazardChecker plugin > > Is support for the existing hazard detectors working now? [it does not > say DONE or WIP here, but your comment below implies, I think, that it > is at least partially working]. Glad you're interested. I can explain. We have several important tools in LLVM that most sch...

...option: In review (Sergei) > - Bidirectional list scheduling: DONE > - LiveInterval Update: WIP (simple instruction reordering is > supported) > - Target-independent precise modeling of register pressure: DONE > - Register pressure reduction scheduler: WIP > - Support for existing HazardChecker plugin Is support for the existing hazard detectors working now? [it does not say DONE or WIP here, but your comment below implies, I think, that it is at least partially working]. > - New target description feature: buffered resources > - Modeling min latency, expected latency, and resourc...

...edulers. As much as possible, the standard scheduling algorithm will be built from standalone utilities and data structures. The customizations that you describe would all be handled by providing a new MachineSchedStrategy. Start by composing your scheduler from the pieces that are available, e.g. HazardChecker, RegisterPressure... (There's not much value providing a scheduling queue abstraction on top of vector or priority_queue). From that point, we can improve the design. Here's what you can expect in the MachineScheduler: 1. Precise register pressure tracking with back off. I'm in the pr...

...ONE - AliasAnalysis aware DAG option: In review (Sergei) - Bidirectional list scheduling: DONE - LiveInterval Update: WIP (simple instruction reordering is supported) - Target-independent precise modeling of register pressure: DONE - Register pressure reduction scheduler: WIP - Support for existing HazardChecker plugin - New target description feature: buffered resources - Modeling min latency, expected latency, and resources constraints - Heuristics that balance interlocks, regpressure, latency and buffered resources For targets where scheduling is critical, I encourage developers who stay in sync with t...

...duling algorithm will be built > from standalone utilities and data structures. The customizations that > you describe would all be handled by providing a new > MachineSchedStrategy. Makes sense to me. > Start by composing your scheduler from the pieces that are available, > e.g. HazardChecker, RegisterPressure... (There's not much value > providing a scheduling queue abstraction on top of vector or > priority_queue). What do you mean by this last point? We absolutely want to be able to swap out different queue implementations. There is a significant compile time tradeoff to...

...al list scheduling: DONE > >> - LiveInterval Update: WIP (simple instruction reordering is > >> supported) > >> - Target-independent precise modeling of register pressure: DONE > >> - Register pressure reduction scheduler: WIP > >> - Support for existing HazardChecker plugin > > > > Is support for the existing hazard detectors working now? [it does > not > > say DONE or WIP here, but your comment below implies, I think, that > it > > is at least partially working]. > > Glad you're interested. I can explain. We have severa...

Hey Everyone, I'd like to begin a project to rework the scheduler to address some problems we've discovered on this end. The goal is to get a more configurable/flexible scheduler while simplifying maintenance by separating policy from implementation to get independent and interchangeable parts. This is going to be challenging because we are still stuck on LLVM 2.9. We will be upgrading

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.

...anism. > ... > I'm glad to hear the top-down scheduler will get some attention. We'll > be wanting to use that. Out of curiosity what about top-down works better for your target? > >> Start by composing your scheduler from the pieces that are available, >> e.g. HazardChecker, RegisterPressure... (There's not much value >> providing a scheduling queue abstraction on top of vector or >> priority_queue). > > What do you mean by this last point? We absolutely want to be able to > swap out different queue implementations. There is a significant &...