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

SystemVerilog operator overloading (bind construct) #633

Closed
veripoolbot opened this issue Mar 13, 2013 · 1 comment
Closed

SystemVerilog operator overloading (bind construct) #633

veripoolbot opened this issue Mar 13, 2013 · 1 comment
Labels
resolution: wontfix Closed; work won't continue on an issue or pull request

Comments

@veripoolbot
Copy link
Contributor


Author Name: Yves Mathieu
Original Redmine Issue: 633 from https://www.veripool.org
Original Date: 2013-03-13


Operator overloading is supported by SystemVerilog standard (chap 11.11 in 1800_2012 version).
To my knowledge no commercial simulation or synthesis tool has any support for this feature.

This feature is already supported by CAD tools for many years for VHDL language, furthermore the recently standardised VHDL fixed-point and floating point (synthesizable) packages use operator overloading.

I wonder what would be the cost of supporting this feature:
-1 - for simulation
-2 - for synthesis : Verilator could be used as a translator from "SystemVerilog" to "SystemVerilog" to target synthesis tools that do not support this feature

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2013-03-16T00:32:20Z


Generic classes would need to be supported first, followed by many other things that synthesis/simulators DO support. So unless you are willing to put some good time in to help it along I don't expect attention would go towards this for several years.

@veripoolbot veripoolbot added the resolution: wontfix Closed; work won't continue on an issue or pull request label Dec 22, 2019
tgorochowik pushed a commit to antmicro/verilator that referenced this issue Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: wontfix Closed; work won't continue on an issue or pull request
Projects
None yet
Development

No branches or pull requests

1 participant