3
0
Fork 0
mirror of https://github.com/YosysHQ/yosys synced 2025-06-27 16:38:46 +00:00

bugpoint.rst: How to sv-bugpoint

This commit is contained in:
Krystine Sherwin 2025-06-14 14:28:43 +12:00
parent f8cc37d22e
commit d5e48ce75a
No known key found for this signature in database

View file

@ -287,7 +287,7 @@ the ``-expect error "<string>" 1`` option to perform a similar role to
is still valid.
.. code-block:: bash
:caption: Example test.sh
:caption: Example test.sh for C-Reduce
:name: egtest
#!/bin/bash
@ -320,6 +320,25 @@ minimize the design to just the failing code, while still being valid Verilog.
end endmodule
sv-bugpoint
~~~~~~~~~~~
sv-bugpoint works quite similarly to C-Reduce, except it requires an output
directory to be provided and the check script needs to accept the target file as
an input argument: ``sv-bugpoint outDir/ test.sh test.v``
.. code-block:: bash
:caption: Example test.sh for sv-bugpoint
#!/bin/bash
verilator --lint-only $1 &&/
yosys -p "logger -expect error \"unsupported\" 1; read_verilog $1"
Notice that the commands for ``yosys -p`` are now in double quotes (``"``), and
the quotes around the error string are escaped (``\"``). This is necessary for
the ``$1`` argument subsitution to work correctly.
Doing it manually
~~~~~~~~~~~~~~~~~