[M3commit] CVS Update: cm3

[Jay]

It is, you know, a reasonable message.

One might wonder how we avoided it?

Mark all locals volatile in functions with try/raise/fatal?

 

 - Jay

 


From: jay.krell at cornell.edu
To: hosking at cs.purdue.edu
Date: Mon, 11 May 2009 06:47:49 +0000
CC: m3commit at elegosoft.com
Subject: Re: [M3commit] CVS Update: cm3



I don't think so.
 
  - Jay
 


From: hosking at cs.purdue.edu
To: hosking at cs.purdue.edu
Date: Mon, 11 May 2009 15:19:31 +1000
CC: m3commit at elegosoft.com; jay.krell at cornell.edu
Subject: Re: [M3commit] CVS Update: cm3




Jay,


Have you changed something about how the compiler invokes setjmp/longjmp for exception handling?


-- Tony


On 11 May 2009, at 15:18, Tony Hosking wrote:

We didn't used to get these errors with -O3.  I don't know what has changed with the compiler backend, but something new is happening.  We should check the logs to see the last time I pushed through -O3, and figure out what changed since. 






On 11 May 2009, at 14:48, Jay wrote:

I got a lot of those warnings when I tried -O3.
And one error running the result that I didn't look into.
 
 - Jay

 
> Date: Mon, 11 May 2009 05:24:22 +0000
> To: m3commit at elegosoft.com
> From: hosking at elego.de
> Subject: [M3commit] CVS Update: cm3
> 
> CVSROOT: /usr/cvs
> Changes by: hosking at birch. 09/05/11 05:24:22
> 
> Modified files:
> cm3/m3-libs/m3core/src/runtime/POSIX/: RTPerfTool.m3 
> 
> Log message:
> Avoid warning:
> 
> ../src/runtime/POSIX/RTPerfTool.m3: In function 'RTPerfTool__StartTool':
> ../src/runtime/POSIX/RTPerfTool.m3:125: warning: variable 'M3_AcxOUs_execResult' might be clobbered by 'longjmp' or 'vfork'
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20090511/e7cb0acb/attachment-0002.html>