[M3commit] CVS Update: cm3

[Tony Hosking]

I'm not convinced there is any more -O3 breakage than this.

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

>
> ps: We load/store everything as a bitfield as I understand..I wonder  
> if that is a problem, like, given that bitfields aren't addressible..
>
> (which is not to say that they can't be volatile, and bitfields are  
> often used to "map to hardware interfaces" so maybe this is  
> irrelevant)
>
>
>
> Tony -- your change..is it reasonable/useful in light of larger  
> related -O3 breakage?
>
>
>
> - Jay
>
>
>
> From: jay.krell at cornell.edu
> To: hosking at cs.purdue.edu
> CC: m3commit at elegosoft.com
> Subject: RE: [M3commit] CVS Update: cm3
> Date: Mon, 11 May 2009 07:39:16 +0000
>
>
>
> 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..
>
> 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