Skip to content
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

Fuizzer: Internal Error Unlinked interface after unsupported interface error #1561

Closed
veripoolbot opened this issue Oct 16, 2019 · 1 comment
Closed

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Oct 16, 2019


Author Name: Eric Rippey
Original Redmine Issue: 1561 from https://www.veripool.org


With the attached testcase, running:

verilator_bin --lint-only 3.sv

with version:

Verilator 4.020 devel rev v4.020-19-gc73336f

Produces:

%Warning-MULTITOP: 3.sv:1: Multiple top level modules
: ... Suggest see manual; fix the duplicates, or use --top-module to select top.
... Use "/* verilator lint_off MULTITOP */" and lint_on around source to disable this message.
: ... Top module 'm'
module m(i.p bus);
^
: ... Top module 'i'
module m(i.p bus);
^
%Error: 3.sv:1: Unsupported: Interfaced port on top level module
module m(i.p bus);
^~~
%Error: 3.sv:1: Cannot find file containing interface: 'i'
module m(i.p bus);
^
%Error: Internal Error: 3.sv:1: ../V3LinkDot.cpp:2047: Unlinked interface
module m(i.p bus);
^

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Oct 16, 2019


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-10-16T23:43:03Z


Going to ignore internal errors after normal errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.