-
Notifications
You must be signed in to change notification settings - Fork 12
Modular subtype #221
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
Modular subtype #221
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable.
c7d6b76
to
b17b194
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks reasonable to me, might be worth adding a range_check test for modular subtypes though?
Lower_Bound_Value : Integer; | ||
Upper_Bound_Value : Integer; | ||
begin | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be worth asserting that followed_mod_type
is actually an unsigned
or mod_type
b17b194
to
3f2f88c
Compare
bound-mod-type for non-power-two modulus and bounded-unsignedbv-type for power-two modulus.
By following the origin mod type and extracting the bounds.
regarding the new bounded types.
taken from UKNI and simplified a bit. Also includes a range check.
and so we need to extend the range checking interface to accept unsigned.
3f2f88c
to
708484e
Compare
Adds the initial support for modular subtypes. Operators for the new type are nor included in this PR.