[M3devel] Are all 5 gcc branches used?

[Jay K]

They likely aren't all used.I'd like to make none of them used, but that is another matter.

Look in src/m3makefile.

I think OpenBSD targets might be back on gcc-4.2.There is flexibility in there, in m3makefile and "parse.c", but maybe at too high cost.

The problem, you can imagine, is that Apple has as fork, OpenBSD has a fork, we have a fork, and there is mainline.Ideally everyone would be in mainline and nobody would have any forks.

As we/I move from major version to version, I generally make a new fork.

I have a certain paranoia and laziness when debugging -- "does it work with the old one" -- "how easy is to reconstruct the old one? Oh, cool, it is still right there, I don't have to figure out how to go backwards in source control, and I can easily have them both side by side". I realize source control could help me here.

It also allows for "staging", i.e. I can bring in new version, test some targets, but leave the other targets alone, waiting for myself or others to test them later. Or, decide they are little enough used just move them forward w/o testing.

If gcc obsoletes targets we want to keep, we could keep the old versions. Not super useful given our usage levels.

We could maybe also minimize our changes and distribute patches only.Sometimes maybe I went overboard with my changes.

Or we could ditch gcc entirely and use the C backend and/or LLVM, hopefully both unpatched. :)

Try xz instead of gzip, maybe it halves the size?

 - Jay


> Date: Wed, 3 Jun 2015 13:57:38 +0200
> From: adacore at marino.st
> To: m3devel at elegosoft.com
> Subject: [M3devel] Are all 5 gcc branches used?
> 
> I see 5 gcc branches in m3-sys/m3cc.  I've seen gcc-4.7 in use and I can
> guess gcc-apple is still used, but are gcc, gcc-4.5, and gcc-4.6
> branches obsolete?
> 
> There reason why it matters is that I'm using github's built-in "create
> tarball from top of repo" capability as the digest-confirmed source
> distribution file.  All the extra gcc branches are causing the
> compressed tarball to be pretty big.  Currently it's at 150Mb.
> 
> If some of these gcc branches are unused and will never again be used, I
> might suggest they are pruned.  It's in the repository so they could be
> retrieved with the right hash, and it would dramatically reduce the size
> of the archive tarball.
> 
> If all 5 versions of gcc are still used then that's a horse of a
> different color.
> 
> John
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150603/607e9906/attachment-0002.html>