Skip to content

SystemVerilog: detect import conflicts#1693

Draft
kroening wants to merge 1 commit intomainfrom
verilog-import-conflicts
Draft

SystemVerilog: detect import conflicts#1693
kroening wants to merge 1 commit intomainfrom
verilog-import-conflicts

Conversation

@kroening
Copy link
Copy Markdown
Collaborator

@kroening kroening commented Mar 3, 2026

Per IEEE 1800-2017 section 26.3, this adds error detection for:

  • Direct imports that conflict with local declarations
  • Wildcard imports that are used in expressions and then redeclared

Wildcard imports that are not used remain 'potentially locally visible' and can be shadowed by local declarations.

import6.sv
--bound 0
^EXIT=2$
^EXIT=6$
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here and below: can we also include a check for the presence of an error message?

import8.sv
--bound 0
^EXIT=2$
^EXIT=6$
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here: test for the error message.

Per IEEE 1800-2017 section 26.3, this adds error detection for:
- Direct imports that conflict with local declarations
- Wildcard imports that are used in expressions and then redeclared

Wildcard imports that are not used remain 'potentially locally visible'
and can be shadowed by local declarations.
@kroening kroening force-pushed the verilog-import-conflicts branch from 73a7ae7 to 78b2190 Compare April 9, 2026 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants