|Progress in instruction scheduling? email@example.com (Stephan Ceram) (2008-03-17)|
|Re: Progress in instruction scheduling? firstname.lastname@example.org (=?UTF-8?B?IO+7i++7pO+6riDvuqnvu6vvu6Dvu67vu68=?=) (2008-03-18)|
|Re: Progress in instruction scheduling? email@example.com (Ivan Boldyrev) (2008-03-19)|
|Re: Progress in instruction scheduling? SidTouati@inria.fr (Sid Touati) (2008-04-22)|
|From:||Sid Touati <SidTouati@inria.fr>|
|Date:||Tue, 22 Apr 2008 11:18:26 +0200|
|Posted-Date:||22 Apr 2008 10:23:41 EDT|
> There is some recent work on optimal scheduling which compares with
> the list scheduling heuristic. The problem is that the list scheduler
> is very close to optimal and much faster than the optimal one.
Sorry to contradict you, list schedulers are far from the optimal,
twice the optimal in extreme case...
For very small basic blocks, list schedulers are good, as any scheduling
The problem comes when considering large basic blocks, which is the most
common codes: for large basic blocks, you cannot compute optimal
instruction schedules easily (because it is an NP-complete problem), so
you cannot compare list schedulers to optimal schedulers.
Return to the
Search the comp.compilers archives again.