[M3commit] CVS Update: cm3

[Tony Hosking]

You are conflating two distinct issues here.  volatize is there for a different reason, and should retain its name.

On 5 Jul 2010, at 17:26, Jay K wrote:

> 
> 
> attached
> 
> 
> ----------------------------------------
>> Date: Mon, 5 Jul 2010 23:25:58 +0000
>> To: m3commit at elegosoft.com
>> From: jkrell at elego.de
>> Subject: [M3commit] CVS Update: cm3
>> 
>> CVSROOT: /usr/cvs
>> Changes by: jkrell at birch. 10/07/05 23:25:58
>> 
>> Modified files:
>> cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.c
>> 
>> Log message:
>> rename "volatize" to "make_volatile"
>> move existing code to function m3cg_make_volatile which
>> will work for being called from front end, if we decide to do that
>> (not done here)
>> no real change here, just some renaming
>> 
>> Note that the terminology is a bit off perhaps, in that
>> I believe "volatile function" to gcc backend means
>> "noreturn function". Here it means "all the locals, parameters,
>> temporaries are volatile". ie. function calls setjmp/vfork.
>> (This is actually overkill of course: it should only make
>> volatile stuff used after the second return; this could actually
>> still be defeating a fair amount of volatile removal -- any
>> function with a "try".)
>> 
> 		 	   		  <rename_volatize.txt>