mirror of
https://github.com/YosysHQ/yosys
synced 2025-04-29 11:55:52 +00:00
024bfcdc53
Calling :cmd:title:`<cmd>` will generate a cross reference to `<cmd>`, but unlike :cmd:ref: which displays a literal block and puts the title (short_help) in the hovertext (the title field of an a-ref), :cmd:title: will display "<cmd> - <short_help>" as plain text. Thus replacing the previous use case of referring to :doc:`cmd/<cmd>`. Also refactor util py scripts to have more descriptive names.
28 lines
990 B
ReStructuredText
28 lines
990 B
ReStructuredText
Synth commands
|
|
--------------
|
|
|
|
.. todo:: comment on common ``synth_*`` options, like ``-run``
|
|
|
|
Packaged ``synth_*`` commands
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
A list of all synth commands included in Yosys for different platforms can be
|
|
found under :doc:`/cmd/index_techlibs`. Each command runs a script of sub
|
|
commands specific to the platform being targeted. Note that not all of these
|
|
scripts are actively maintained and may not be up-to-date.
|
|
|
|
General synthesis
|
|
~~~~~~~~~~~~~~~~~
|
|
|
|
In addition to the above hardware-specific synth commands, there is also
|
|
:cmd:title:`prep`. This command is limited to coarse-grain synthesis, without
|
|
getting into any architecture-specific mappings or optimizations. Among other
|
|
things, this is useful for design verification.
|
|
|
|
The following commands are executed by the `prep` command:
|
|
|
|
.. literalinclude:: /code_examples/macro_commands/prep.ys
|
|
:start-at: begin:
|
|
|
|
:doc:`/getting_started/example_synth` covers most of these commands and what
|
|
they do.
|