[M3commit] CVS Update: cm3

Jay K jay.krell at cornell.edu
Sun Jul 25 03:57:55 CEST 2010


I'm pretty sure the three way merge I did will tolerate it ok.
A human should tolerate it easily too.
I don't look through the CVS history to find the diffs, I diff against baseline gcc 4.3.0, 4.3.5, etc.
  (btw, in doing so, I found another label thing we did, have to come back to 4.5.0 work soon..)
But if you insist, ok.

 - Jay

________________________________
> From: hosking at cs.purdue.edu
> Date: Sat, 24 Jul 2010 13:42:06 -0400
> To: jkrell at elego.de
> CC: m3commit at elegosoft.com
> Subject: Re: [M3commit] CVS Update: cm3
>
> Do we really want to dirty the gcc diffs from the original sources in
> this way. It will make sifting the diffs a nightmare for future ports.
>
> Antony Hosking | Associate Professor | Computer Science | Purdue University
> 305 N. University Street | West Lafayette | IN 47907 | USA
> Office +1 765 494 6001 | Mobile +1 765 427 5484
>
>
>
>
> On 24 Jul 2010, at 16:33, Jay Krell wrote:
>
> CVSROOT: /usr/cvs
> Changes by: jkrell at birch. 10/07/24 16:33:16
>
> Modified files:
> cm3/m3-sys/m3cc/gcc/gcc/: tree-ssa-forwprop.c
>
> Log message:
> tree-ssa-forwprop.c: In function `forward_propagate_into_cond':
> tree-ssa-forwprop.c:362: warning: `name' might be used uninitialized in
> this function
>
 		 	   		  


More information about the M3commit mailing list