A2.1.6 Every Thread Must Finish

MediumDebug15 minKey: IEEE 1800-2017, checkedReview the topic

A range followed by more: follow each thread to its end, and say where each attempt passes, fails or is still waiting.

Hardware context: A request answered by an acknowledge and then a completion, within a window. Follow every thread of the window before calling a request failed.

After a request, ack must come one to three edges later, and done one edge after that ack.

The trace gives the sampled values at twelve rising edges. Five attempts are asked. For each, choose its verdict and the edge where it is decided.

The Assertion and the Trace

Req |-> ##[1:3] Ack ##1 Donereq |-> ##[1:3] ack ##1 done
req |-> ##[1:3] ack ##1 doneAttempts start at edge 1 (t=5), edge 2 (t=15), edge 5 (t=45), edge 9 (t=85), edge 11 (t=105).edgetime1521532543554565576587598510951110512115clkreqackdoneattemptsattempt @5?attempt @15?attempt @45?attempt @85?attempt @105?
Scroll horizontally ↔
Read the sampled values as text
  • req: edge 1 = 1, edge 2 = 0, edge 3 = 0, edge 4 = 0, edge 5 = 1, edge 6 = 0, edge 7 = 0, edge 8 = 0, edge 9 = 1, edge 10 = 0, edge 11 = 1, edge 12 = 0
  • ack: edge 1 = 0, edge 2 = 1, edge 3 = 0, edge 4 = 1, edge 5 = 0, edge 6 = 1, edge 7 = 0, edge 8 = 0, edge 9 = 0, edge 10 = 1, edge 11 = 0, edge 12 = 0
  • done: edge 1 = 0, edge 2 = 0, edge 3 = 0, edge 4 = 0, edge 5 = 1, edge 6 = 0, edge 7 = 0, edge 8 = 0, edge 9 = 0, edge 10 = 0, edge 11 = 1, edge 12 = 0

Standard behaviour: no free simulator runs this construct correctly. The key was derived by hand from IEEE 1800-2017 and checked independently.

Simulator note: Verilator 5.052 misses the failure of a range followed by more (lesson A2.1). The key is the standard behaviour, derived by hand and checked by the trace oracle.

How to Answer

For each attempt, choose its verdict and the edge where that verdict is decided. A vacuous attempt is graded on its verdict only. A pending one is still running at the end of the run.

  • Answer every attempt: its verdict, and the edge where that verdict is decided.
  • Read the values the assertion samples at each edge (the dots), not the values after the edge.
  • Run grades the first attempt and says whether it is right. Submit grades every attempt and says only whether all are right.
Full specification
The assertion
a4: assert property (@(posedge clk) req |-> ##[1:3] ack ##1 done);

The clock rises at 5, 15, 25, ... 115. The run ends at 120.

Hints

Hint 1

Write out the three threads of each attempt: which edges must hold ack, and which must hold done?

Hint 2

One thread dying is not the attempt failing.

Hint 3

A thread that needs an edge after the run is still open.

What is checked: The verdict and decision edge of five attempts, against the key in docs/sva-standard-traces/A2.md (sva-040-b), checked by its oracle.

More problems on this topic

Report a problem with this page

Your answers 5 attemptsSaved locally

req |-> ##[1:3] ack ##1 done

AttemptVerdictDecided atResult
attempt @5starts at edge 1 (t=5)
attempt @15starts at edge 2 (t=15)
attempt @45starts at edge 5 (t=45)
attempt @85starts at edge 9 (t=85)
attempt @105starts at edge 11 (t=105)

Edges and times match the trace figure. Your answers stay in this browser until you submit.

Not checked yet

Run checks the first attempt. Submit checks every attempt.

Key: IEEE 1800-2017, checked