llvm dev - Feb 2016 - Extending DFAPacketizer for the new machine model instead of itineraries

Hello,

I have a VLIW architecture that is described with the new machine model.
I would like to use DFA packetizer for the final stages of
scheduling/packetization, but it only uses itineraries as the source of the
scheduling information.

Are there any plans for the packetizer to be extended to use new machine
model?

Or, do you have any estimation about how difficult it would be to do this?

Thank you in advance,
F
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160209/1435cc0b/attachment.html>

The main difficulty would be in generating the state table for the DFA. 
The packetizer itself just tries to allocate resources in the packet 
using the the DFA.
 From the Hexagon perspective, we don't have any immediate plans to 
replace it with another model.

-Krzysztof

On 2/9/2016 9:28 AM, Fatum Niaerdh via llvm-dev wrote:
>
> I have a VLIW architecture that is described with the new machine model.
> I would like to use DFA packetizer for the final stages of
> scheduling/packetization, but it only uses itineraries as the source of
> the scheduling information.
>
> Are there any plans for the packetizer to be extended to use new machine
> model?
>
> Or, do you have any estimation about how difficult it would be to do this?
>
> Thank you in advance,
> F
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, 
hosted by The Linux Foundation