[llvm-dev] [VLIW Scheduler] Itineraries vs. per operand scheduling
陳韋任 via llvm-dev
llvm-dev at lists.llvm.org
Mon Feb 5 04:55:21 PST 2018
> I also found this thread from almost 2 years ago:
> At that time it seemed the itineraries are a better choice, but is it
> still the case?
> Also, in this thread Phil says:
> “Some of the constraints that can be found in in-order micro architectures
> cannot be expressed in the per-operand scheduling model”
> Does anybody have an example of such constraints that will be harder to
> model with per operand scheduling?
From the thread you provided, it says
ARM might be a good start for generic superscalar. Hexagon for VLIW style
Anyway, I also interest in knowing their difference. :-)
Wei-Ren Chen (陳韋任)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev