You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: