Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:This is borderline ridiculous (Score 2) 311

No, really, it is Steve Job's fault - personally - that since the devices are loved so much by users, the re-sale black market price is high allowing big profits for people who steal them. If ONLY Steve Job made the products lousy, no one would pay for them! and no one would steal them!

Uh.... I wonder if the criminals DON'T steal the Android phones?

Criminal: "Give me your iPhone!"

Geek: "I have an Android phone!"

Criminal: "Darn, ok you can keep your Android."


Comment Re:Holy slanted summary, Batman! (Score 1) 476

Good points. So the issue is really with the GPL license enforceability....

I wonder if the same issues are at hand with GCCXML : http://www.gccxml.org/HTML/Index.html

One could make a library that just spawns a sub-process running GCCXML, then grab the result and pass the appropriate parts of the parse tree to the caller.

No linking involved, no GPL violations either.

Comment Re:I often disagree with RMS, but... (Score 1) 476

That's not true in general, and not true specifically when generating SIMD code for SSE4 or ARM NEON.

All the latest GCC versions 4.4, 4.5, 4.6 have serious regressions in SIMD optimizations, it actually went backwards in efficiency over the years.

Final code efficiency is the primary reason why I needed to switch to Clang.

It is a real pain btw to have to have two C compilers for a single embedded device!

Comment Re:I often disagree with RMS, but... (Score 1) 476

...More like the barber shows you the cool new shaver that you didn't understand and that he helped design.

An interesting exercise is to compare the internals of Clang, written in more modern C++ versus gcc, written in C, and to decide for yourself which one you'd rather maintain.



Note that Clang is written in modern C++ and is also faster than GCC.

One benchmark shown is that clang loading a parse tree of 'precompiled headers' is almost the same time as it takes to just compile the headers.

FWIW, I'm switching to Clang wherever it is supported because of all of the regressions in GCC for vectorization in C and C++ since GCC 4.2

Comment Re:Holy slanted summary, Batman! (Score 1) 476

This is what I don't understand - If GCC is under the GPL, and was modified to be a library, under the GPL the front ends / library clients that use it would ALSO have to be released under the GPL. The original developers had no problem with that. So what, exactly, would the problem be for RMS? It could only have increased the pervasiveness of GNU/GCC. And if there was some problem that RMS knows about then this would be a problem with the specific license that GCC uses.

Comment Re:Holy slanted summary, Batman! (Score 3, Informative) 476


Also, one of the interesting points about the primary reasoning behind the creation of the CLANG compiler was not because of the GPL license.

it was because the developers wanted to make GCC more powerful, so that it could be used as a library.

Stallman refused to allow the features to be added even though they were not asking for the GPL licensing to be changed.

So the developers started CLANG. In c++. as a library.

Watch this for some very interesting history and features:


Slashdot Top Deals

If at first you don't succeed, you are running about average.