From: Evan L. <sa2...@cy...> - 2021-01-28 20:29:54
|
On 28/01/2021 18:54, Cary R. via Iverilog-devel wrote: > For your case where you know what you are doing and > it has been thought out I would just disable the warning. > An excellent idea, but... The wiki says warnings should be prefixed with 'no-' to disable them. After some experimentation it turns out that you need to put a space after the 'W', and the 'no-' before the 'timescale' (ie. '-W no-timescale'). This works for the case I described, but then the case I described only generates a warning if you compile with '-Wtimescale' anyway, so this just restores the default behaviour. If you have a more serious case in which some earlier modules have no explicit timescale, and a later one does, '-W no-timescale' *doesn't* turn off the warning. You could argue that, in this case, the user should get a warning and shouldn't be able to turn it off. So maybe it's not a problem, and just needs some documentation that this warning can't in general be disabled. Actually, a good option might be to implement a '-timescale' command-line option for a default timescale (I think everyone else does this), and then just remove the warning completely. |