Skip to content

SystemVerilog: named properties #579

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

Merged
merged 2 commits into from
Jun 30, 2024
Merged

SystemVerilog: named properties #579

merged 2 commits into from
Jun 30, 2024

Conversation

kroening
Copy link
Member

This adds support for SystemVerilog named properties.

Concurrent assertion items (assert/assume/cover) that are module items with
a block label go into the module name space, not into a separate "property"
name space.

Assertion items without block item now get a label based on the kind of the
assertion item (assert/assume/cover).
@kroening kroening force-pushed the named_property1 branch 2 times, most recently from a613ace to f7c6ec7 Compare June 24, 2024 22:38
@kroening kroening marked this pull request as ready for review June 24, 2024 22:39
This adds support for SystemVerilog named properties.
CORE
named_property1.sv
--bound 0
^\[main\.assert\.1\] always main\.x == 10: PROVED up to bound 0$
Copy link
Collaborator

Choose a reason for hiding this comment

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

Wouldn't it make sense for x_is_ten to be used here in some way?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'd like that -- it would require splitting up the type checking phase such that the initial phase doesn't expand symbols marked as "macro". Will do eventually.

Copy link
Member Author

Choose a reason for hiding this comment

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

@kroening kroening merged commit e746526 into main Jun 30, 2024
6 checks passed
@kroening kroening deleted the named_property1 branch June 30, 2024 07:39
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