[M3devel] pruning m3cc/gcc?

[Jay]

[trying to untruncate again, though I think Tony quoted the whole thing]


----------------------------------------
> From: jay
> To: m3devel; hosking
> Subject: pruning m3cc/gcc?
> Date: Mon, 29 Jun 2009 03:38:28 +0000
>
>
> I keep thinking of deleting
>
[snip, parts of gcc]
>
> We don't use any of it.
> Some of these deletions would shorten our build command lines.
> Though some (esp. fixincludes and maybe libgcc) might break the
> shortest configure + make that the "real" cm3 doesn't use but can be useful.
>
>
> I didn't include them in gcc-interix and gcc-apple.
>
>
> But there are two possible contradictory goals:
>
>
> - just have what we use/change
> - have a complete merged gcc tree from which you
> could build gcc/cc1 and not just cm3cg
> Except we don't have C++, Java, Ada, Fortran,
> so we don't really have this, but C probably counts for something.
>
>
> If the second is the goal, don't delete.
> If the first is the goal, delete.
>
>
> There is also "having it all there in case it is needed
> or somesuch", but that's easy enough to get elsewhere.
>
>
> - Jay