Claire Xen  🏳️‍⚧️ 🏳️‍🌈 🧙🏻‍♀️ BLM  🏴 🚩

I don’t see a problem (no sarcasm).

It's a race condition in simulation. You need to use a non-blocking assignment (<=) or other "always @(posedge clk)" blocks will see either the old or the new dout value in that same cycle, depending on the implementation defined order the simulator runs those blocks in.

Oh dear. Am I correct in understanding that using any blocking assignment in a clocked always block, where the value is used outside the block, can always lead to a race condition, because the simulation order of triggered clocked always blocks is unknown?