[M3commit] CVS Update: cm3

[Tony Hosking]

It turns out not actually to be used by m3front.  But it is defined by m3middle, so let's support it and not get bitten in the arse if/when m3front ever uses it.

On 3 Mar 2010, at 18:45, Jay K wrote:

>  I don't see where it is used.
>  I built all of "std" with the gcc_assert(0) and <* ASSERT FALSE *> (in m3back).
>  The parameters are being passed to memset in the wrong order.
>  Compare it to m3cg_zero.
>  I was actually looking to see if parameters are left to right or right to left, I looked at these two examples and decided they can't both be correct.
>  
>  - Jay
>  
> From: hosking at cs.purdue.edu
> Date: Wed, 3 Mar 2010 11:02:36 -0500
> To: hosking at cs.purdue.edu
> CC: m3commit at elegosoft.com
> Subject: Re: [M3commit] CVS Update: cm3
> 
> Please say how this is broken.
> 
> On 3 Mar 2010, at 10:57, Tony Hosking wrote:
> 
> Huh?  I see it in the front-end!
> 
> 
> On 3 Mar 2010, at 10:21, Jay Krell wrote:
> 
> CVSROOT: /usr/cvs
> Changes by: jkrell at birch. 10/03/03 10:21:42
> 
> Modified files:
> cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.c 
> 
> Log message:
> zero_n is incorrect and never used, put gcc_assert(0) in it
> 
> 
> 

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