cliffordwolf
commented
6 years ago Yosys uses special functions to log warnings and errors. But there is no API yet for writing them to an extra file. (By in -q mode only warnings and errors are printed to stdout.)
The Yosys command stat prints resource usage statistics. You can run something like tee -o stat.txt stat as last command in your Yosys script.
Practically all of the Yosys log is "Optimisations applied" and "Transformations". You can run a command with trace to print additional trace information for every design change caused by the command (for example trace opt).
qaarah
proppy
Does Project IceStorm toolchain (yosys, arachne-pnr, IceStorm Tools) have some type of standard output format for getting reports about things like;
Messages like info, warnings & errors (for all stages)
Synthesis information like;
Place & Route like;
The reason I'm asking is that in my CI system, I would like to track how a design is changing over time. For example, I would like to understand if merging a change will dramatically increase resource usage, introduce new warnings, etc.
I don't quite know what would be the most useful to track yet, so also open to suggestions there :-). I don't really want the extreme low level details, more high level and hierarchical summaries.
I eventually hope to write some crappy Python scripts which translate the proprietary tools (like Vivado and ISE) into the Yosys / OpenFPGA formats to reuse the tracking for designs I can't yet use the open tools for.
Thank you for your help!