Chaim Frenkel wrote: > No scanning. I was considering that all variables on a store would > safe store the previous value in a thread specific holding area[*]. Then > upon a deadlock/rollback, the changed values would be restored. > > (This restoration should be valid, since the change could not have taken > place without an exclusive lock on the variable.) > > Then the execution stack and program counter would be reset to the > checkpoint. And then restarted. Sigh. Think about references. No, think harder. See? -- Alan Burlison
- Re: RFC 178 (v2) Lightweight Threads Nick Ing-Simmons
- Re: RFC 178 (v2) Lightweight Threads Alan Burlison
- Re: RFC 178 (v2) Lightweight Threads Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Alan Burlison
- Re: RFC 178 (v2) Lightweight Threads Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Nick Ing-Simmons
- Re: RFC 178 (v2) Lightweight Threads Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Nick Ing-Simmons
- Re: RFC 178 (v2) Lightweight Threads Alan Burlison
- Re: RFC 178 (v2) Lightweight Threads Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Alan Burlison
- Re: RFC 178 (v2) Lightweight Threads Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Alan Burlison
- Re: RFC 178 (v2) Lightweight Threads Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Dan Sugalski
- Re: RFC 178 (v2) Lightweight Threads Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Dan Sugalski
- Re: RFC 178 (v2) Lightweight Threads Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Dan Sugalski
- Re: RFC 178 (v2) Lightweight Threads Alan Burlison
- Re: RFC 178 (v2) Lightweight Threads Nick Ing-Simmons