Re: [myhdl-list] What logic is allowed inside an always_comb?
Brought to you by:
jandecaluwe
From: Ben R. <be...@re...> - 2016-02-22 22:13:27
|
That's exactly the documentation I was looking for. Thank you! On Mon, Feb 22, 2016 at 2:49 PM, Christopher Felton <chr...@gm...> wrote: > On 2/21/2016 8:59 PM, Ben Reynwar wrote: > > Is there a summary of the kind of logic that one can use inside an > > @always_comb without confusing MyHDL's black parsing magic? > > > > I attempted to do: > > > > @always_comb > > def dostuff(): > > for i, o in ((i1, o1), (i2, o2)): > > o.next = i > > > > but it didn't behave, > > When you say it didn't "behave", do you mean it > didn't simulate as expected or it didn't convert? > > Code like the above will not convert, what is > convertible is covered in the manual: > > http://docs.myhdl.org/en/stable/manual/conversion.html#the-convertible-subset > > For simulation only, I believe it is the goal > to support all constructs. But realistically > this might be difficult as your example > demonstrates(?). We will need to investigate > your example and determine if it is an expected > limitation or a bug. > > Regards, > Chris > > > > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > |