From: Cary R. <cy...@ya...> - 2021-01-02 20:51:36
|
Also what is supported needs to be enabled otherwise they are completely ignored. There are some known limitation/bug in what is implemented. SDF back annotation is also partially supported. As I remember the last big thing added was state-dependent path delays, but SDF support for that is not possible given the information that is passed to the runtime since we need to match delays based on equations. I used to work on specify/SDF from time to time, but once we started working on SystemVerilog that is where all my time has gone. One thing that is blocking most of the specify bugs and the implementation of the timing checks is the ability to calculate expressions as pull items (at the consumers request) not as push items (the changing variables propagate through the expression network). This broken behavior creates races and zero time glitches. I started a rework for the base expressions as standalone code, but it has been almost a decade since I touched it :(. When I get back to it I will be changing the code to support move semantics and other thing available in C++11 or later. Cary On Saturday, January 2, 2021, 10:14:45 AM PST, Evan Lavelle <sa2...@cy...> wrote: Thanks, missed that page. On 02/01/2021 17:53, Martin Whitaker wrote: > On 02/01/2021 17:16, Evan Lavelle wrote: >> What's the status of specify block support? Are timing checks meant to >> work? >> > No, timing checks are ignored. > > Missing features are listed here: > > https://iverilog.fandom.com/wiki/Release_Notes_Icarus_Verilog_11#Things_That_Still_Don.27t_Work > > > although I don't promise that list is complete. > > > _______________________________________________ > Iverilog-devel mailing list > Ive...@li... > https://lists.sourceforge.net/lists/listinfo/iverilog-devel _______________________________________________ Iverilog-devel mailing list Ive...@li... https://lists.sourceforge.net/lists/listinfo/iverilog-devel |