Skip to content

Verilog: elaboration per compilation unit#1561

Merged
kroening merged 1 commit intomainfrom
verilog_elaborate_unit
Feb 10, 2026
Merged

Verilog: elaboration per compilation unit#1561
kroening merged 1 commit intomainfrom
verilog_elaborate_unit

Conversation

@kroening
Copy link
Copy Markdown
Collaborator

@kroening kroening commented Jan 3, 2026

IEEE 1800 2017 3.12.1 requires compliant tools to compile "compilation units" separately, with a compilation unit scope.

This breaks out a function that elaborates a compilation unit by itself.

@kroening kroening force-pushed the verilog_elaborate_unit branch 2 times, most recently from 625fc67 to 191f108 Compare January 4, 2026 16:41
IEEE 1800 2017 3.12.1 requires compliant tools to compile "compilation
units" separately, with a compilation unit scope.

This breaks out a function that elaborates a compilation unit by itself.
@kroening kroening force-pushed the verilog_elaborate_unit branch from 191f108 to 97d2bc0 Compare February 9, 2026 20:04
@kroening kroening marked this pull request as ready for review February 9, 2026 21:36
void verilog_elaborate_compilation_unit(
const verilog_parse_treet &parse_tree,
symbol_table_baset &symbol_table,
message_handlert &message_handler)
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.

There doesn't seem to be a need for a message_handlert here?!

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

It will come -- next, this will elaborate compilation-unit scoped typedefs, functions, etc.

@kroening kroening merged commit c4dee34 into main Feb 10, 2026
11 checks passed
@kroening kroening deleted the verilog_elaborate_unit branch February 10, 2026 17:29
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