[Gems-users] Rationale: Aborting with Lazy Version Management doesn't take effect immediately

["Fuad Tabba" <fuad@xxxxxxxxxxxxxxxxx>]

Hi,

A question on ruby/transactional memory when using Lazy Version Management. I've noticed that when a transaction aborts, it doesn't abort immediately, but sets an abort flag (setAbortFlag) which gets processed at the next load, store or commit (readyToRetireMemRef and commitTransaction).

My question is why doesn't the transaction abort immediately? Is is a modeling issue or a workaround to something gems/simics related?

Thanks.

Cheers,
/fuad