[M3commit] CVS Update: cm3

[Tony Hosking]

We already volatilise as necessary for setjmp/longjmp (at least we did when last I looked, because I remember putting it in).

I would prefer to avoid volatile in all other situations where possible.


On 7 Jul 2010, at 15:54, Jay K wrote:

> 
> But I admit I'm nervous about removing all the volatile, esp. on stores.
> We should have a bunch of tests using exceptions that access locals/parameters in except and finally blocks.
> I'm willing to put back volatile on all stores.
> Or even loads if there is justification.
> 
> I thought there'd be a setjmp in all functions with try/except/finally, and therefore the same
> pessimization, but now I'm not sure of that.
> 
>  - Jay
> 
> ----------------------------------------
>> From: jay.krell at cornell.edu
>> To: hosking at cs.purdue.edu; jkrell at elego.de
>> Date: Wed, 7 Jul 2010 19:13:02 +0000
>> CC: m3commit at elegosoft.com
>> Subject: Re: [M3commit] CVS Update: cm3
>> 
>> 
>> Back when all loads and stores were volatile!
>> And the optimizer was severely hampered. Any optimized code I looked at was full of unnecessary code.
>> Which do you prefer?
>> 
>> - Jay
>> 
>> ----------------------------------------
>>> From: hosking at cs.purdue.edu
>>> Date: Wed, 7 Jul 2010 11:56:30 -0400
>>> To: jkrell at elego.de
>>> CC: m3commit at elegosoft.com
>>> Subject: Re: [M3commit] CVS Update: cm3
>>> 
>>> This is new. It used to work!
>>> 
>>> 
>>> On 7 Jul 2010, at 08:20, Jay Krell wrote:
>>> 
>>>> CVSROOT: /usr/cvs
>>>> Changes by: jkrell at birch. 10/07/07 08:20:57
>>>> 
>>>> Modified files:
>>>> cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.c
>>>> 
>>>> Log message:
>>>> partial redundancy elimination ('pre') also crashes compiling libm3/Formatter, add comment; remove all the other stuff about disabling optimizations
>>> 
>> 
>