[libre-riscv-dev] [Bug 178] first coriolis2 tutorial, workflow and "test project" page

[bugzilla-daemon at libre-riscv.org]

http://bugs.libre-riscv.org/show_bug.cgi?id=178

--- Comment #23 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---


On Sunday, February 16, 2020, Jean-Paul Chaput <Jean-Paul.Chaput at lip6.fr>
wrote:

> yep done, added already, and replied.

  Caramba ! Encore raté !
     -- Tintin, L'Oreille Cassée.

:)


  My apologies here, the LIP6 spam filter is still tagging some,
  but not all, of your messages as spam,

it is utterly bizarre.  are you allowed to ask admins for whitelisting?



> > The Makefile system was the quickest way to stitch together the
> > design flow. In the long run, what I would try is to wrap each
> > external (non-Coriolis2 tool) in a Python wrapper, so making a
> > design will be one big Python script.
> 
> 
> ok interesting. ( i quite like Makefiles, because of their ability to
> handle file dependencies)

  I was having the feeling that the whole Makefile system was reaching
  an "obfuscation limit" and would deter people using it.

things like \$$macroname, these are where i personally would draw a line.

having python tools that are called *by* Makefiles because make works out that
to generate file X.ext from X.ext2, doing that job in python, is a nuisance.

when it goes recursive, it gets even more hairy in python (bear in mind we need
to do a hierarchical layout, not a "full automated and pray" one)

so for example, we need to generate the netlist not from a hardcoded list that
goes into the top level Makefile, we need a *program* that generates that
information, based on what comes out of the *nmigen* conversion to ilang.


  The idea of Python wrapper is to be able to manage some kind of
  "meta-information" across the whole design flow. And, hopefully,
  reduce the obfuscation of the Makefile by using object oriented
  structuration.
    And lastly (but very long term) to seamlessly switch from a
  wrapped old tool to a shiny new one directly implemented in
  Coriolis...

:)

-- 
You are receiving this mail because:
You are on the CC list for the bug.