[M3commit] CVS Update: cm3

Tony Hosking hosking at cs.purdue.edu
Mon May 11 11:17:08 CEST 2009

On 11 May 2009, at 17:39, Jay wrote:

> ah. Notice that m3_load/m3_store mark a lot of things volatile.
> I'm trying out a wild guess and marking "v" volatile before the  
> offseting in those functions..

No, volatile is not what you want.  Flow analysis should be able to  
keep some variables in registers.

> I guess though you've revealed the answer -- strive for like I said  
> -- mark anything volatile referenced in finally or such. Er,  
> anything referenced both in try and finally, something like that.  
> Initial lameness would be all locals in a function with try/finally/ 
> lock. And, gosh, I hope they don't enregister globals. :(
> You'd want some volatile on globals too.
> Only the uses in a try where the function also references them in a  
> finally

I don't think we really want to go down this path.

More information about the M3commit mailing list