[Bug translator/7033] Optimize locking reginon of global variables

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2008-11-14 23:42 -------
A long time ago, this is how we used to do things.
Some reasons against it:

- generated code was much longer, as each use of those
  globals had to be protected individually
- greater likelihood of deadlocks (which would be detected by
  *trylock timeout loops, but that still takes time)
- by the time such a deadlock is detected, we can't roll back
  the prior code run by the probe handler, so we end up with
  inconsistent state


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=7033

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.