What logic is allowed inside an always_comb?
Ben Reynwar <[email protected]> Sun, 21 Feb 2016 19:59:04 -0700
| Newsgroups | gmane.comp.python.myhdl |
|---|---|
| Message-ID | <CAHXOypqC=_wH2W=Yb8zYHsyEAV000Dv-CcHUeex9gK7u-pjFcw@mail.gmail.com> |
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, and looking into the implementation of always_comb I
can see that the "for" loop is not compatible. It decides that i1, o1, i2
and o2 are all inputs and that there are no outputs.
I had a look at the documentation but didn't see a summary anywhere of the
kind of logic that I'm allowed to use here. Does such a summary exist?
It's quite possible that I just read over it.
Cheers,
Ben
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/myhdl-list