Command Line Reference
Reference information about all command line options.
Display help text about command line options and exit.
Display slang version information and exit.
Don't print non-essential output status.
Paths to files that should be included in the compilation.
Causes the tool to treat all input files as being part of a single compilation unit. By default all files are considered to be separate compilation units and ordering between them does not matter. When this option is provided, all files are concatenated together, in order, to produce a single compilation unit.
Adds a file to the compilation, like a positional argument, except that the file is considered to be a Verilog library. Libraries are always their own compilation unit even when compiling with
--single-unit, and modules within them are never automatically instantiated.
Opens the given "command file" containing lists of arguments to process in addition to the ones provided on the command line itself. Any file paths in the file are relative to the current working directory.
See Command Files for more information about command files.
Opens the given "command file" containing lists of arguments to process in addition to the ones provided on the command line itself. Any file paths in the file are relative to the command file itself.
See Command Files for more information about command files.
Any provided positional arguments that have extensions matching <ext> will be ignored. This option is typically used when projects have existing command files listing sources that are not SystemVerilog code.
These options control what action the tool will perform when run. They are mutually exclusive. If none of these are provided, the default action is to elaborate the design, print any diagnostics, and exit.
Treat all files as a single input file (as if
--single-unit had been passed), run the preprocessor on them, and then print the preprocessed text to stdout. If errors occur during preprocessing, they will be printed instead of the preprocessed text.
Run the preprocessor on all input files, print out any macros that are discovered, and exit. No diagnostics will be printed.
Perform parsing of all input files but don't perform type checking and elaboration. All diagnostics encountered will be printed.
Only perform linting of code, don't try to elaborate a full hierarchy.
Include paths and macros
-I,--include-directory <dir> +incdir+<dir>[+<dir>...]
Add the given directory path to the list of directories searched by `include directives that use quotes to specify the path.
Add the given directory path to the list of directories searched by `include directives that use angle brackets to specify the path.
-D,--define-macro <macro>=<value> +define+<macro>=<value>[+<macro>=<value>...]
Define <macro> to <value> (or
1 if <value> is ommitted) at the start of all source files. Example:
slang -DFOO=2 -DBAR=asdf -D BAZ=3
Undefine the given macro at the start of all source files.
When running in preprocessor-only mode (using
-E) include comments in the preprocessed output text.
When running in preprocessor-only mode (using
-E) include directives in the preprocessed output text.
Set the maximum depth of nested include files. Exceeding this limit will cause an error. The default is 1024.
If true, library files will inherit macro definitions from the primary source files. By default library files are independent and will not inherit macros from the main project.
--single-unit must also be passed when this option is used.
Causes all identifiers in the preprocessed output to be replaced with obfuscated alphanumeric strings.
Set the maximum depth of nested language elements. This is a measure of the depth of the parsing stack, which is checked against this limit to avoid stack overflows. The default is 1024.
Set the maximum number of errors that can occur during lexing before the rest of the file is skipped. The default is 64.
Add the given directory path to the list of directories searched when an unknown module instantiation or package import is encountered. Combined with
--libext, files are automatically included based on the name that is unknown. This list is empty by default.
The search works as follows: all known modules, interfaces, programs, packages, and classes add their names to a list of known definitions. Any instantiations, package import directives, or double colon-scoped names that reference a name not in the list of known definitions will trigger a search in all library directories, trying all specified library extensions. If a matching file is found it will be loaded and parsed in its entirety, and the algorithm will be triggered again on any new names found.
Add the given extension to the list of extensions tried when searching for files to satisfy unknown module instantiations and package imports. This list automatically includes '.v' and '.sv' by default.
Dump the compiled AST in JSON format to the specified file, or '-' for stdout.
When dumping AST to JSON, include only the scope (or symbol) specified by the given hierarchical path. This option can be specified more than once to include more than one scope. If not provided, all symbols are dumped.
Specifies the name of a module that should be instantiated at the root of the design. Can be specified more than once to instantiate multiple top-level modules. The module specified must not have any non-defaulted parameters or interface ports.
If no top modules are specified manually, they will be automatically inferred by finding all modules that are not instantiated elsewhere in the design.
Set the maximum depth of the design hierarchy. Used to detect infinite module instantiation recursion. The default is 128.
Set the maximum number of steps that can occur during generate block evaluation before giving up. Used to detect infinite generate loops. The default is 131072.
Set the maximum depth of the constant evaluation call stack. Used to detect infinite recursion during constant evaluation. The default is 128.
Set the maximum number of steps that can occur during constant evaluation before giving up. Used to detect infinite constant evaluation loops. The default is 100000.
Set the maximum number of frames to show when printing a constant evaluation backtrace in diagnostics; the rest will be abbreviated to avoid spamming output. The default is 10.
Set the maximum number of instances allowed in a single instance array. The limit exists to prevent runaway compilation times on invalid input. The default is 65535.
Attempt to increase compatibility with the specified tool. Various options will be set and warnings will be silenced to mimic the given tool as closely as possible. Currently only 'vcs' is supported as a value.
Select which expressions in min:typ:max triplets should be processed as part of the compilation. By default this will be the "typical", or middle expression.
Specifies a default time scale to use for design elements that don't explicitly provide one. If this option is not set, there is no default and an error will be issued if not all elements have a time scale specified. Example:
Override all parameters with the given name in top-level modules to the provided value. This option can be specified more than once to override multiple parameters.
Don't issue an error if an identifier is used before its declaration. This is not allowed in SystemVerilog – this option is provided for compatibility with tools that have weaker enforcement of this rule.
Allow hierarchical references in constant expressions. SystemVerilog doesn't permit this, but many popular tools allow it anyway so this flag can be used for compatibility purposes.
Allow all integral types to convert implicitly to enum types in assignments. SystemVerilog doesn't permit this, but some tools allow it anyway so this flag can be used for compatibility purposes.
Allow signals driven by always_comb or always_ff procedures to also be driven by initial blocks. SystemVerilog doesn't permit this, but some tools allow it anyway so this flag can be used for compatibility purposes.
Perform strict driver checking, which currently means disabling procedural 'for' Driver loop unrolling
Always print diagnostics in color. If this option is unset, colors will be enabled if a color-capable terminal is detected.
Show or hide column numbers in diagnostic output. The default is to show.
Show or hide location information (file name, line and column numbers) in diagnostic output. The default is to show.
Show or hide source code and caret location in diagnostic output. The default is to show.
Show or hide warning option names in diagnostic output. The default is to show.
Show or hide file include stacks in diagnostic output. The default is to show.
Show or hide macro expansion backtraces in diagnostic output. The default is to show.
Show or hide hierarchy locations in diagnostic output. The default is to show.
One or more paths in which to suppress warnings. Use this if you want to generally turn on warnings for your project and have it build cleanly but have some files which you can't modify for some reason.
Set a limit on the number of errors that will be printed. Setting this to zero will disable the limit. The default is 64.
Don't issue an error for instantiations of unknown modules, interface, and programs.
Enable warning "foo". See Warning Reference for a complete list of warnings that can be enabled this way.
Disable warning "foo".
Disable all warnings.
Enable all warnings.
Treat all warnings as errors.
Treat warning "foo" as an error.
Turn warning "foo" into a warning even if
-Werror is specified.
Legacy Vendor Command Support
Define rule to ignore vendor command <vendor_cmd> with its following <N> parameters. A command of the form +xyz will also match any vendor command of the form +xyz+abc, as +abc is the command's argument, and doesn't need to be matched. This option is typically used to ignore commands listed in command files that are meant for some other tool.
Define rule to rename vendor command <vendor_cmd> into existing <slang_cmd>. Similarly to
--cmd-ignore, this exists to support existing command files that specify options with different names.
Some tool vendors declare custom preprocessor directives, and slang fails when encountering those. By using this command line option with the vendor's directive, it will be ignored (the vendor directive should be specified without the leading ` symbol). It is possible to use this command line option multiple times, to ignore multiple vendor directives. Please note that any vendor directive ignored also ignores all optional parameters until the end of the line.
Run slang with time tracing enabled, which collects information about how long various parts of the compilation take. When the program exits it will write the trace results to the given file, which is JSON text containing events in the Chrome Trace Event format.