<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10pt"><div><span>Hello,</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><span>This actually should forego another thread, but anyhow:</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style:
normal;">For overall 'general purpose' usage, a 'patched' GCC 4.7.2 version is requested.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><span style="background-color: transparent;">All interim releases of GCC >=4.4.4 can build Illumos-gate - if properly patched.</span><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;">RFE: Patch and update
SFEgcc to GCC 4.7.2, for a unified C/C++ compiler effort for 'all' https://hg.openindiana.org/upstream -based building efforts and FOSS-based porting projects.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><span style="background-color: transparent;">~ Ken Mays</span><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color:
rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'Courier New', courier, monaco, monospace, sans-serif; background-color: transparent; font-style: normal;"><br></div><div><br></div> <div style="font-family: 'Courier New', courier, monaco, monospace, sans-serif; font-size: 10pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Nick Zivkovic <zivkovic.nick@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> OpenIndiana Developer mailing list <oi-dev@openindiana.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, January 27, 2013 10:24 AM<br> <b><span style="font-weight:
bold;">Subject:</span></b> Re: [oi-dev] Compiler migration #2<br> </font> </div> <br>
All good points. Just want to chime in and say that for userland C<br>code development, gcc3 is adequate. I don't think anyone will see some<br>huge, practical benefit from a bleeding edge C compiler.<br><br>For C++11 development, it seems that there is no choice but use the<br>latest and greatest. It's a shame that major apps are written in C++<br>and not C (like firefox).<br><br>Although I do have a question. If gcc3 is deemed more desirable than<br>gcc4 because it generates code that can run on i386, and isn't<br>specialized, then why did the Illumos engineers switch the kernel<br>compiler to gcc4 from sunstudio, and not to gcc3 from sunstudio.<br><br>Thanks.<br><br>On Sun, Jan 27, 2013 at 9:10 AM, Jim Klimov <<a ymailto="mailto:jimklimov@cos.ru" href="mailto:jimklimov@cos.ru">jimklimov@cos.ru</a>> wrote:<br>> On 2013-01-26 20:57, Bob Friesenhahn wrote:<br>>><br>>> GCC 4.4 does not produce code for modern CPUs whereas GCC is
continually<br>>> enhanced to be able to produce code which targets modern CPUs.<br>><br>><br>> And in terms of prepackaged generic distribution that works on i386<br>> and above, how can targeting of modern CPUs be a useful bonus and<br>> not a drawback? This was stressed by Luca's question:<br>><br>><br>>> The only possible workarounds are build a recent gcc version yourself or<br>>> use<br>>> SFEgcc package, but the last option is not a viable alternative if your<br>>> CPU is<br>>> not SSE2-capable. So, not every users are able to use that<br>>> compiler/runtime.<br>><br>><br>> I do know that there are solutions to my questions, and a couple of<br>> months ago we've discussed them (i.e. prebuilt HW-specific libraries<br>> lofs-mounted over a common filename, as is <a target="_blank" href="http://libc.so/">libc.so</a>; or usage of UBE<br>> unified binary
executables).<br>><br>> I just wanted to raise this concern - that newest is not always the<br>> best when you deal with such heterogenous environments. I am "for"<br>> the optimized code running on machines and using their CPUs in the<br>> best possible manner, but this should be specially catered for by<br>> the distro - so that these newest CPUs aren't the only ones capable<br>> of running this distro ;)<br>><br>> My 2c,<br>> //Jim Klimov<br>><br>><br>><br>> _______________________________________________<br>> oi-dev mailing list<br>> <a ymailto="mailto:oi-dev@openindiana.org" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br>> http://openindiana.org/mailman/listinfo/oi-dev<br><br>_______________________________________________<br>oi-dev mailing list<br><a ymailto="mailto:oi-dev@openindiana.org" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br><a
href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank">http://openindiana.org/mailman/listinfo/oi-dev</a><br><br><br> </div> </div> </div></body></html>