[M3devel] reducing use of volatile in backend?

[Tony Hosking]

We don't want to disable optimisations for types where it makes sense  
to have them. Better to smarten up typebased alias analysis instead so  
we can get rid of volatile properly.

Sent from my iPhone

On Jun 1, 2010, at 12:16 PM, Jay K <jay.krell at cornell.edu> wrote:

>
> Tony, would we maybe be better off not using volatile everywhere but
> selectively turning off optimizations in m3_post_options?
> You know, using volatile probably disables more than necessary?
> I'm experimenting with this.
>
>  - Jay
>
>
>
>
>