Re: [myhdl-list] MEP - keep hierarchy in conversion

[Per K. <bas...@gm...>]

Enforcing "top-level convertibility" at all levels of the design would be a
huge step backwards for MyHDL. I have not looked into MEP107, it may take
away some of that sting, but that will not help a pre-MEP107 design (such
as mine). Not even my top module is "top-level convertible", I have a
script to wrap it for conversion.

Encapsulating target dependent design is standard practice, but the netlist
hierarchy is not part of that---mostly. :)
(You can never be too careful with those generalizations.)

Cheers
Per

On Wed, Oct 2, 2013 at 9:28 AM, Jan Decaluwe <ja...@ja...> wrote:
[...]

> Simply convert at various levels, and use user-defined code
> (under parameter control) for instantations.
>
> [...]

> I have seen many cases of vendor lock-in with a very high
> economical cost that could perfectly have been avoided.
> Conversely, my own experience has been to use HDL design
> to keep dependencies minimal - with considerable success.
>
[...]

> Jan
>
> --
> Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
>      Python as a HDL: http://www.myhdl.org
>      VHDL development, the modern way: http://www.sigasi.com
>      World-class digital design: http://www.easics.com
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
> _______________________________________________
> myhdl-list mailing list
> myh...@li...
> https://lists.sourceforge.net/lists/listinfo/myhdl-list
>