Skip to content
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

(Allegedly) more SV unrecognised syntax #186

Closed
veripoolbot opened this issue Nov 16, 2009 · 2 comments
Closed

(Allegedly) more SV unrecognised syntax #186

veripoolbot opened this issue Nov 16, 2009 · 2 comments

Comments

@veripoolbot
Copy link
Collaborator

@veripoolbot veripoolbot commented Nov 16, 2009


Author Name: vesselin kavalov (@vessko)
Original Redmine Issue: 186 from https://www.veripool.org
Original Date: 2009-11-16


Please see the attached files! Please excuse if multiple files fail for the same root cause - I tried hard to uniquify the failures but may have not done very good job ;(
vess

@veripoolbot

This comment has been minimized.

Copy link
Collaborator Author

@veripoolbot veripoolbot commented Nov 16, 2009


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2009-11-16T21:24:48Z


I'm sorry about this but I'm not under NDA with your company and we both need to honor the copyrights in the files, unless you can state you own the copyright - and no it's not enough to just strip the comments :) I'm deleting them.

I think there's real issues here, but I really need a issue for each major problem including a "sanitized" few lines of each construct that is causing problems. For example from what you emailed separately:

module bugas;
    initial begin
       ASSERT_CHK: assert (0) else $error("%m -- not allowed %d", 0);
    end
endmodule

Sorry, but this is part of the "cost" to you of open source.

@veripoolbot

This comment has been minimized.

Copy link
Collaborator Author

@veripoolbot veripoolbot commented Nov 16, 2009


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2009-11-16T21:37:22Z


BTW your #� was a fine example, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.