-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Add Support for Input Filelist Option #4456
Comments
... Our project is currently using a simple script to bridge this gap from straight filelist to a Makefile list. |
Well, the most literal interpretation of this isn't possible:
and I use |
It sounds to me that the functionality is already provided in |
Verific is indeed great, and also used within many proprietary tools, including Vivado. It is however not opensource.
BTW, while Verific (unfortunately 😢) seems the only Yosys recourse for proper SV support, the |
If someone implements the |
@Ravenslofty any suggestions on a better suggestion? Would Let's note that |
I'd be happy to try to find a quick workaround. Is your intention to re-use this file for other commands, like to pass to a simulator? |
Yes. A typical part of the Reuse Methodology is to have one-and-only-one filelist that brings in all RTL files of the entire design, or an IP block. This filelist is then used for all downstream tools that process the design RTL, from Linter on. Note that |
Hi, I have created a PR to implement this feature #4926 |
Currently, Yosys requires specifying each file individually in the command line or script for synthesis or formal analysis. This can be cumbersome for large projects with many files. I propose the addition of an input filelist option, where Yosys can read a file containing a list of Verilog source files to be included in the synthesis run. This feature would streamline the process, especially for larger projects or those with many dependencies.
The text was updated successfully, but these errors were encountered: