<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>The bulk of this is commited now -- 4.3/4.5/4.6 removal.<div>gcc-apple and gmp remain, for now. </div><div><br></div><div>Any objections and I can add them back.</div><div><br></div><div>We can also trim the frontends and libraries from 4.7 and apple.</div><div><br></div><div>Thank you,</div><div> - Jay<br><br><br><div><hr id="stopSpelling">From: jay.krell@cornell.edu<br>To: m3devel@elegosoft.com<br>Date: Tue, 9 Jun 2015 18:30:17 +0000<br>Subject: [M3devel] gcc-4.3/4.5/4.6 ?<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr"><div> Is there any interest in maintaining </div><div><br></div><div><br></div><div> 1) gcc/m3cg/parse.c support for gcc 4.3/4.5/4.6? </div><div>It is slightly messy.</div><div><br></div><div><br> 1b) gcc 4.2? This is where hypothetical ARM_DARWIN support is, last I checked, years ago. </div><div><br></div><div><br> 2) gcc-4.3/4.5/4.6 in-tree? </div><div><br></div><div><br> Or remove them to keep checkouts smaller? There was complaint as to our<br> source tree size, and these directories do add a lot of size for little gain. </div><div><br></div><div><br> They were historically useful to transition versions. I don't think it was wrong<br> to have the temporary growth. </div><div><br></div><div><br> All targets except for ARM_DARWIN default to gcc 4.7. </div><div><br></div><div><br> Do people often/ever go back and compare/debug?<br></div><div><br></div><div> Or want to retain that ability, with the current ease?<br></div><div><br></div><div><br></div><div> Or ok to get the files from history, for that rare-to-never event? </div><div><br></div><div><br></div><div><br></div><div><br></div><div> If we do maintain the gcc backend, I would likely import as gcc-5.1 etc., and recreate the problem, but<br> it can be a "rolling" problem and fix. But I'm not keen on maintaining the gcc backend anyway.</div><div><br></div><div><br> - Jay<br></div> </div></div></div> </div></body>
</html>