[M3commit] m3_build vs. build in parse.c?

Tony Hosking hosking at cs.purdue.edu
Thu Mar 4 08:58:30 CET 2010


So that we can avoid having to analyse all the constants ourselves.  We can simply generate the trees and then have gcc fold them.

On 4 Mar 2010, at 02:16, Jay K wrote:

> Why use one vs. the other?
> It appears that they are equivalent *except* that m3_build attempts to optimize,
> but falls back to build if it can't.
>  
> That is, m3_build calls fold_build.
>  
>  - Jay
> 
> 
> 
> 




More information about the M3commit mailing list