<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 11, 2016, at 1:46 PM, Michael Kuperstein via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">To the best of my understanding - because we want to be able to bootstrap clang with the system compiler that ships with various linux and BSD distributions.<div class="">Windows has no equivalent concept.</div></div></div></blockquote>I mean no offense to linux/BSD developers, but should we have a discussion (in another thread perhaps) about whether its reasonable to treat them specially in this regard?</div><div><br class=""></div><div>Both macOS and Windows developers need to download compilers separately to be LLVM developers. Why shouldn’t linux/BSD developers? </div><div><br class=""></div><div>Given that we ship prebuilt binaries for many distros, it seems like its easy to get a new enough compiler. This way we won’t be faced with the problem of old GCCs holding us back in future.</div><div><br class=""></div><div>Pete<br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><br class=""></div><div class="">(This is probably not a good enough reason to keep GCC 4.7 support, but it apparently is for GCC 4.8).</div><div class=""><br class=""></div><div class="">Michael</div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Oct 11, 2016 at 10:28 AM, Martin J. O'Riordan via llvm-dev <span dir="ltr" class=""><<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Why is it more important to be backward compatible with ancient versions of GCC than relatively more recent versions of Visual Studio? We are removing support for VS2013 because of defects in that product, yet GCC v4.7.x is more ancient than VS2013, so why should the answer be any different?<br class="">
<br class="">
Devil's Advocate,<br class="">
<br class="">
MartinO<br class="">
<div class="HOEnZb"><div class="h5"><br class="">
-----Original Message-----<br class="">
From: llvm-dev [mailto:<a href="mailto:llvm-dev-bounces@lists.llvm.org" class="">llvm-dev-bounces@<wbr class="">lists.llvm.org</a>] On Behalf Of Renato Golin via llvm-dev<br class="">
Sent: 11 October 2016 18:01<br class="">
To: Sylvain Bertrand <<a href="mailto:sylvain.bertrand@gmail.com" class="">sylvain.bertrand@gmail.com</a>><br class="">
Cc: llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>>; Peter Collingbourne <<a href="mailto:pcc@google.com" class="">pcc@google.com</a>><br class="">
Subject: Re: [llvm-dev] unable to compile llvm with gcc 4.7.4<br class="">
<br class="">
On 11 October 2016 at 17:35, <<a href="mailto:sylvain.bertrand@gmail.com" class="">sylvain.bertrand@gmail.com</a>> wrote:<br class="">
> Those bots should have been the first to be set up. Hope you can fix this soon.<br class="">
<br class="">
We had 4.7 bots for a long time, but migrations happen, and we probably (separately) didn't expect to be the last 4.7 ones. This was a coordination problem.<br class="">
<br class="">
Now, there are talks to upgrade the GCC version from 4.7, but we can't do 4.9 because many stable distributions still 4.8, but we can do 4.8, which has enough buildbots (and will for the long term).<br class="">
<br class="">
I'm not saying this is a "fix" for your problem, but your problem would happen any time soon when we move the GCC version up anyway.<br class="">
<br class="">
Can you upgrade to 4.8?<br class="">
<br class="">
cheers,<br class="">
--renato<br class="">
______________________________<wbr class="">_________________<br class="">
LLVM Developers mailing list<br class="">
<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/<wbr class="">mailman/listinfo/llvm-dev</a><br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
LLVM Developers mailing list<br class="">
<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/<wbr class="">mailman/listinfo/llvm-dev</a><br class="">
</div></div></blockquote></div><br class=""></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></body></html>