[M3devel] Are all 5 gcc branches used?
Jay K
jay.krell at cornell.edu
Wed Jun 10 23:57:53 CEST 2015
By "gcc obsolete targets", I meant that latest gcc might not target systems that we can/do.Not that gcc versions are no longer maintained. Maybe not all that interesting.
We had surprisingly recent usage on OSF/1 v4.0. I had wanted to get Irix working. And AIXand I had an older system.
Anyway, I forgot about this part of it, and we could targetthem with the C backend instead of gcc. Or make current gcc work.
The size is better now?
- Jay
> Date: Wed, 3 Jun 2015 20:10:07 +0200
> From: adacore at marino.st
> To: jay.krell at cornell.edu; m3devel at elegosoft.com
> Subject: Re: [M3devel] Are all 5 gcc branches used?
>
> On 6/3/2015 20:04, Jay K wrote:
> > If gcc obsoletes targets we want to keep, we could keep the old
> > versions. Not super useful given our usage levels.
>
> It has. gcc-4.7 is a closed branch. Only gcc 4.8 and later are not
> obsolete by that definition, so all 5 of these are obsolete.
>
> I would definitely encourage to prune as many of these as possible. I
> could probably challenge OpenBSD as well, e.g. Assuming you saying "4.2"
> based on the base compiler, why are you assuming it must be built by
> base compiler?
>
> By definition, the base compiler is only required to build base. There
> are much newer and well maintained versions of gcc in openbsd ports
> tree. There's no reason a ports compiler couldn't be used (I assume
> this is actually common).
>
> > Try xz instead of gzip, maybe it halves the size?
>
> I can't influence github's API. It is what it is.
>
> John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150610/02cf1686/attachment-0002.html>
More information about the M3devel
mailing list