The command synthruns the recommended script for general purpose synthesis tasks. See help synthfor a complete list of commands invoked by this meta command.
Your script must either borrow from synthor just call synthto get general-purpose material. Many scenarios are called synth -run coarsefor the coarse-grained part of the synthesis, and then continue to tune the sequence of commands for the synthesis of small grains. See for example synth_xilinx.
To synthesize an ASIC in a library in freedom format, use the following script as a starting point:
read_verilog mydesign.v
synth -top mytop
dfflibmap -liberty mycells.lib
abc -liberty mycells.lib
clean
write_verilog synth.v
For scripts that perform a formal review, a less aggressive set of optimizations is often required. In this case, the following sequence of commands is usually a good starting point for the “synthesis” part of the formal verification flow:
hierarchy [-check -top <top-module>]
proc; opt; memory [-nomap]; opt -fast; check -assert
source
share