[M3commit] CVS Update: cm3

Tony Hosking hosking at cs.purdue.edu
Mon May 11 07:18:03 CEST 2009


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/b59f8de6/attachment-0002.html>


More information about the M3commit mailing list