[core] Synchronous, Rational Clock Domains#5270
Merged
Conversation
Add new APIs for describing synchronous and rational clock domains. These deprecate and replace the old `derived` API for creating a synchronous clock domain derived from another. This change is necessary to, when coupled with property assertions, error when weaker synchronizers are used in places where stronger synchronizers are needed. E.g., this will allow us to error if a synchronous synchronizer is used to cross between clock domains which are asynchronous or rational. Assisted-by: Claude:claude-sonnet-4-6 Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
seldridge
added
Feature
jackkoenig
approved these changes
Apr 17, 2026
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
2 participants
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.
Add new APIs for describing synchronous and rational clock domains. These
deprecate and replace the old
derivedAPI for creating a synchronousclock domain derived from another.
This change is necessary to, when coupled with property assertions, error
when weaker synchronizers are used in places where stronger synchronizers
are needed. E.g., this will allow us to error if a synchronous
synchronizer is used to cross between clock domains which are asynchronous
or rational.
Assisted-by: Claude:claude-sonnet-4-6