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
Hi,
I came across yet another PSL issue. If I have locally clocked PSL assertion in never, NVC
does not accept it:
entity psl18 is
end entity;
architecture tb of psl18 is
signal a,b,c : bit;
begin
-- Covered at 3ns
-- psl one: assert never (a = b) @rising_edge(c);
end architecture;
I get:
nvc -a --psl ../../../nvc/test/regress/psl18.vhd -e psl18 -r
** Error: sorry, clock expressions are only supported at the outermost level of a property
> ../../../nvc/test/regress/psl18.vhd:11
|
11 | -- psl one: assert never (a = b) @rising_edge(c);
| ^^^^^^^^^^^^^^^^^^^^^^^
** Error: property is not in the simple subset as the operand of never is not a Boolean or Sequence
> ../../../nvc/test/regress/psl18.vhd:11
|
11 | -- psl one: assert never (a = b) @rising_edge(c);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
** Error: sorry, unclocked properties are not supported
> ../../../nvc/test/regress/psl18.vhd:11
|
11 | -- psl one: assert never (a = b) @rising_edge(c);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= Note: there is no default clock declaration in this design unit
This worked in GHDL and VCS too.
When I brace the never and use the clocking expression on outermost level as the error indicates:
-- psl one: assert (never (a = b)) @rising_edge(c);
the code analyses fine, but it crashes during elaboration:
Hi,
I came across yet another PSL issue. If I have locally clocked PSL assertion in never, NVC
does not accept it:
I get:
This worked in GHDL and VCS too.
When I brace the
never
and use the clocking expression on outermost level as the error indicates:the code analyses fine, but it crashes during elaboration:
In broader sense, it would be nice to have better support for arbitrary combination of clocking
events e.g. something like:
It may ease things in designs with multiple asynchronous clocks. But I guess this is a lot of work.
The text was updated successfully, but these errors were encountered: