Browse Source

Update PSL next_event_a example as ghdl issue ghdl/ghdl#2157 was fixed

master
T. Meissner 2 years ago
parent
commit
cef17d03f8
2 changed files with 5 additions and 5 deletions
  1. +0
    -1
      README.md
  2. +5
    -4
      src/psl_next_event_a.vhd

+ 0
- 1
README.md View File

@ -100,7 +100,6 @@ The next lists will grow during further development
## Supported, but under investigation
* `next_event_a[i to j]` operator
* `eventually!` behaviour with liveness proofs, see [GHDL issue 1345](https://github.com/ghdl/ghdl/issues/1345)
## Further Ressources


+ 5
- 4
src/psl_next_event_a.vhd View File

@ -32,10 +32,11 @@ begin
default clock is rising_edge(clk);
-- Check for one possible value of b
-- Both assertions should hold
-- Assertions don't hold, assuming GHDL bug
NEXT_EVENT_0_a : assert always ((a and b = x"4") -> next_event_a(c)[1 to 4](b = x"4"));
NEXT_EVENT_1_a : assert always ((a and b = x"5") -> next_event_a(c)[1 to 4](b = x"5"));
-- Both assertions hold (see ghdl/ghdl#2157)
NEXT_EVENT_0_a : assert always ((a and b = x"4") -> next_event_a(c)[1 to 4](b = x"4"))
report "NEXT_EVENT_0_a failed";
NEXT_EVENT_1_a : assert always ((a and b = x"5") -> next_event_a(c)[1 to 4](b = x"5"))
report "NEXT_EVENT_1_a failed";
-- Check for all possible values of b


Loading…
Cancel
Save