Issue #516
suppress multiple warnings for the same issue
| Status: | Closed | Start date: | 05/17/2012 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | Wilson Snyder | % Done: | 0% |
|
| Category: | Usage | |||
| Target version: | - |
Description
In complex designs with multiple instances of the same module, verilator generates multiple warnings for the same issue, e.g.:
%Warning-WIDTH: ...mc_channel.v:575: Operator ASSIGNDLY expects 5 bits on the Assign RHS, but Assign RHS's VARREF 'atc_req_uop_in' generates 4 bits. %Warning-WIDTH: ...mc_channel.v:582: Operator ASSIGNDLY expects 5 bits on the Assign RHS, but Assign RHS's VARREF 'dlc_req_uop_in' generates 4 bits. %Warning-WIDTH: ...mc_channel.v:575: Operator ASSIGNDLY expects 5 bits on the Assign RHS, but Assign RHS's VARREF 'atc_req_uop_in' generates 4 bits. %Warning-WIDTH: ...mc_channel.v:582: Operator ASSIGNDLY expects 5 bits on the Assign RHS, but Assign RHS's VARREF 'dlc_req_uop_in' generates 4 bits.
Of course, this is not critical issue.
History
Updated by Wilson Snyder about 1 year ago
- Category set to Usage
- Status changed from New to Assigned
- Assignee set to Wilson Snyder
Thought I'd knock this off in a few minutes, but forgot about multi line messages.
Anyhow fixed in git towards 3.900+.
Updated by Wilson Snyder about 1 year ago
- Status changed from Assigned to Resolved
Also available in: Atom
![[logo]](/img/veripool_small.png)