Re: [myhdl-list] Ignoring generators

[Christopher F. <chr...@gm...>]

On 9/1/2014 2:57 PM, Uri Nix wrote:
> Hi Chris,
>
> Actually yes: it can be useful when some of the Signals contain high level
> objects that can't be viewed by gtkwave. So a selective trace would allow
> ignoring the complex signal, but allow viewing the timing waves (clk,
> data_valid, etc).

Obviously, I agree :)  I haven't heard any reasons
not to suggest such a feature, once I finish some
other items (fixbv) I will try and propose the
enhancement.

That is exactly how I came across the need, I had
a simulation with some non-convertible generators
doing all kinds of funky stuff (writing files, etc),
but I also wanted to do some Signal tracing to debug
some logic - needless to say all the monitor type
generators didn't need to be analyzed or their Signals
traced, thought this could be useful.

Thanks for the input,
Chris


>
> Cheers,
> Uri
>
>
> On 27 August 2014 18:23, Christopher Felton <chr...@gm...> wrote:
>
>>
>> Does it make sense to have a function attribute that
>> can be set that allows conversion and tracing to ignore
>> a myhdl generator?
>>
>> Example:
>>
>>       @always_comb
>>       def logic():
>>          # some logic
>>       logic.tracing = False
>>       logic.conversion = False
>>
>> Maybe a single attribute "analyze" that would cover both.
>>
>> Regards,
>> Chris
>>
>>
>>