What is wrong with the following code fragment (note the use of non-blocking assignment)?
always@(A or B or C)
begin
E

Question

What is wrong with the following code fragment (note the use of non-blocking assignment)? 
 always@(A or B or C) 
   begin 
     E <= C | B; 
     F <= E ^ A; 
   end

Accepted Answer

Blocking assignment should be used to obtain expected functionality

Answer

E is missing from the sensitivity list

Answer

Latches are implied

Answer

E should not be assigned like this.  Unbuildable “wired-or” logic is implied

Answer

Nothing is wrong with this code fragment.

Crowdly

What is wrong with the following code fragment (note the use of non-blocking ass...

Want instant access to all verified answers on moodle-courses2527.wolfware.ncsu.edu?