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

Two signals can't have the same enum #199

Closed
veripoolbot opened this issue Jan 4, 2010 · 1 comment
Closed

Two signals can't have the same enum #199

veripoolbot opened this issue Jan 4, 2010 · 1 comment
Assignees
Labels
resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800

Comments

@veripoolbot
Copy link
Contributor


Author Name: Byron Bradley (@bbradley)
Original Redmine Issue: 199 from https://www.veripool.org
Original Date: 2010-01-04
Original Assignee: Wilson Snyder (@wsnyder)


Thanks a lot for the work on enums. I tried it on some of our code earlier and got a lot of "Duplicate declaration of enum value" errors. This is caused by creating two signals from the same enum. A patch to show this in test_regress/t/t_enum_int.v is attached and has been tested in another simulator.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2010-01-07T00:08:47Z


Thanks for the test. Fixed in git, along with another problem I found with passing enums across functions.

@veripoolbot veripoolbot added resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800 labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800
Projects
None yet
Development

No branches or pull requests

2 participants