Bugfix: LSU trigger match could cause tracking of split misaligned transactions to get out of sync
Created by: silabs-oysteink
Suppressing LSU valid_0_i on trigger_match_0_i could cause the split_q flag to reset to zero before the last part of an LSU was allowed to go from EX to WB. This could cause an address change and change of the trigger match value.
Updated setting/resetting of split_q to take trigger matches into account.
Added assertions to check that split_q is always 0 when a new LSU instruction enters the EX stage and that the trigger match flag is stable while an LSU instruction remains in EX.
Signed-off-by: Oystein Knauserud Oystein.Knauserud@silabs.com
ed files: