-
Notifications
You must be signed in to change notification settings - Fork 75
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
Non-standard, but defacto standard tests #1227
Comments
CC @hzeller |
I'll add '{} as another invalid syntax that is accepted by commercial tools (verified with VCS). It as expected to represent an empty array. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While looking at more of the blacklisted ivtest tests I am finding that some of these indeed do not match the standard, but are allowed in Icarus because this functionality is support by commercial simulators. Part of our effort has been to be compatible with other simulators and the standard as long as the commercial extensions make sense and do not break compatibility with the standard.
I assume the test suite would be most useful to users if there was a way to designate these common commercial extensions and if they are supported.
For example VCS supports pull gates with multiple terminals. Not sure about any others.
We have comments in the code that NC-verilog supports => between multiple single bit values (e.g. (clk,d => q) = (tR_clk_q,tF_clk_q);) where clk, d and q are all single bit. VCS also supports this functionality
So how do you want to support this kind of behaviour? For now I will just add some documentation.
The text was updated successfully, but these errors were encountered: