[SV] Add elaboration and run-time error/warning/info operations to SV dialect#9601
Merged
[SV] Add elaboration and run-time error/warning/info operations to SV dialect#9601
Conversation
… dialect This adds ErrorOp, WarningOp, and InfoOp for elaboration-time (non-procedural) messages, and ErrorProceduralOp, WarningProceduralOp, and InfoProceduralOp for run-time (procedural) messages. This commit replaces existing usage of run-time message operations to renamed "*.procedural" for the consistency with the rest of SV dialect.
seldridge
approved these changes
Feb 3, 2026
Member
seldridge
left a comment
There was a problem hiding this comment.
LGTM
Thanks for tracking down this! I didn't know about these ops until today. This is making me feel way more confident for things like eventual parameterization.
| let summary = "`$" # severityLower # "` severity message task (run-time)"; | ||
| let description = [{ | ||
| This system task indicates a run-time }] # severityLower # [{. It must be | ||
| used within a procedural region (e.g., `initial`, `always` blocks). |
Member
There was a problem hiding this comment.
Nit, can you include an 1800-2024 section citation for this and the other op?
| sv.info | ||
| } | ||
| } | ||
|
|
86410ff to
df60996
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit refactors the SV dialect's severity message operations to distinguish between run-time (procedural) and elaboration-time (non-procedural) variants, aligning with IEEE 1800-2023 sections 20.10 and 20.11.
Severity message operations are now split into two variants: procedural ops with .procedural suffix (
sv.fatal.procedural, sv.error.procedural, sv.warning.procedural, sv.info.procedural) that must be used within procedural regions like initial or always blocks, and non-procedural ops without suffix (sv.fatal, sv.error, sv.warning, sv.info) that execute during elaboration outside procedural regions for the consistency with the rest of SV dialect.