[Iverilog-devel] Is it time to change the file/line defaults in vvp

[Cary R. <cy...@ya...>]

A long time ago I added support for tracking procedural code lines by emitting information when various commands are executed. The default is when these file/line opcodes are seen in the compiler output they enable this functionality in vvp. To get better error messages in the opcodes I would like to enable emitting the file/line opcode by default and still allow them to be disabled if users are looking for maximum performance and can live with the file/line information missing in the procedural commands warning/error messages. Basically I would switch it to -pfileline=1 as the default and -pfileline=0 can be used to disable emitting the file/line opcodes. I will then update VVP to not automatically emit the per line information, but it will be available for the warning/error messages. If the user wants to emit the per line information they will do this using the control functionality already built into vvp.
The summary is emit file/line opcodes by default in the compiler output, but do not emit the individual file/line information in vvp by default.
Are there any objections?
I personally think it is really bad to emit procedural error messages without corresponding file/line information. I believe I can also add this information to the corresponding assertions to make our debug work easier when things go wrong in the procedural code.

Cary