Linked by Thom Holwerda on Mon 9th Feb 2009 13:24 UTC, submitted by Michael
Benchmarks "In January we published a review of the AMD Shanghai Opteron CPUs on Linux- when we looked at four of the Opteron 2384 models. The performance of these 45nm quad-core workstation/server processors were great when compared to the earlier AMD Barcelona processors on Ubuntu Linux, but how is their performance when running Sun's OpenSolaris operating system? Up for viewing today are dual AMD Shanghai benchmarks when running OpenSolaris 2008.11, Ubuntu 8.10, and a daily build of the forthcoming Ubuntu 9.04 release."
Permalink for comment 348050
To read all comments associated with this story, please click here.
RE[4]: Comment by averycfay
by kaiwai on Tue 10th Feb 2009 15:41 UTC in reply to "RE[3]: Comment by averycfay"
Member since:

Well, arguably you shouldn't be using GCC on OpenSolaris anyway. You should be using the Sun Studio compilers, which are also free and can be installed from the package repository.

Because the Sun compiler isn't compatible with everything out there; XChat will not compile with the Sun compile unless you muck around with a setting inside one of the source code files - IIRC relating to the NTLM proxy authentication. That is one example - I'm sure there are many more out there too.

Again... Because you should be using the Sun Studio compilers with OpenSolaris. Not GCC.

It's not a question of Sun not having their act together here. It's a question of users who switch from Linux not grokking that there are better compilers out there than GCC that they should be using instead when they switch to a different OS.

People would use something other than GCC once their compiler is actually compatible with the source code out there. Yes, the code should be compliant out of the tar ball but at the same time to expect that every project should change their code so that works out of the box with the Sun Studio compiler is just ludicrous. The code is there, for better or worse, its up to Sun to get their compiler to compile code that would compile with gcc. If the code isn't compiling, all the elongated intellectual wankery regarding the superiority of Studio Compiler will be thrown out the window in frustration when someone can't get their opensource application to compile.

The aim should be that people can grab a random application with source code (that compiles on Linux and *BSD) - once it can compile out of the box and with their compilers, then they can say there has been progress. Want proof of the cl*sterf*ck that is Studio compiler, check out the patches upon patches for JDS, pkgbuild's opensource repository, and some things that just can't be built using Studio Compiler - then maybe you'll change your tune.

Edited 2009-02-10 15:46 UTC

Reply Parent Score: 3