[oi-dev] Transitioning from Sun Studio to gcc & clang/llvm

[ken mays]

+1.
 
I'm going to point this out, as I've dealt with C++ development for quite some time.
Stick with GCC/libstdc++ as the baseline.
 
GCC 4.5.2 is preferred. Updating to GCC 4.5.3 is up to OI/Illumos development teams in whole. Don't use GCC 4.6.x for the current oi_151(a-z) stabilization.
 
Usage of other toolsets is up to the developer to do their work - if they so choose clang/llvm/other. Yet, usage of
a reference base of well used/known/documented compiler toolsets between all development teams must maintain top priority to maintain integrity of C++ work as well.
 
~ Ken Mays

From: Andrzej Szeszo <aszeszo at gmail.com>
To: OpenIndiana Developer mailing list <oi-dev at openindiana.org>
Sent: Tuesday, May 24, 2011 4:53 AM
Subject: Re: [oi-dev] Transitioning from Sun Studio to gcc & clang/llvm

On 05/23/11 04:22 PM, Alasdair Lumsden wrote:
> Hi Albert,
> 
> Thanks for the feedback, partial answers inline below!
> 
> On 23 May 2011, at 16:05, Albert Lee wrote:
>> Should we be linking libgcc statically (apparently adds on the order
>> of 10k to every binary) or will every application depend on a package
>> with the gcc libraries?
> Still open for discussion - what are you/others thoughts? Beyond just the on-disk size, there's the in-memory size and presumably a performance difference.
I think I would be after linking libgcc in statically by default. I would help binaries produced by ISVs to be more portable especially after we switch to a newer compiler in the future.
>>> 2. Follow the library layout guidelines set down by SFE
I would look at the guidelines again. If we are deciding that gcc will be the default/official compiler maybe we could use the standard paths for its libraries, etc.
>>> 3. Compile gcc to use Sun ld, but GNU as
+1

As Sun ld and GNU as are recommended by the upstream. http://gcc.gnu.org/install/specific.html

Andrzej

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20110524/a76105e9/attachment-0005.html>