By: Anon (no.delete@this.spam.com), April 12, 2021 12:54 am
Room: Moderated Discussions
Etienne Lorrain (etienne_lorrain.delete@this.yahoo.fr) on April 12, 2021 12:56 am wrote:
> Example of a transactional block which will always fail, whatever the processor
> do: hardware breakpoint (read or write) hit on one of the variable accessed.
Really, I don't see the point here, so what?
1) Will fail, until de breakpoint is removed;
2) Breakpoints may be disallowed or disabled, or postponed inside a transaction, division-by-zero case;
3) Transaction state may be preserved, even if retried, the CPU may skip the breakpoint after firing it for the first time.
I see an attempt search for totally irrelevant corner cases.
> Example of a transactional block which will always fail, whatever the processor
> do: hardware breakpoint (read or write) hit on one of the variable accessed.
Really, I don't see the point here, so what?
1) Will fail, until de breakpoint is removed;
2) Breakpoints may be disallowed or disabled, or postponed inside a transaction, division-by-zero case;
3) Transaction state may be preserved, even if retried, the CPU may skip the breakpoint after firing it for the first time.
I see an attempt search for totally irrelevant corner cases.