A Review of GCC 4.0 429
ChaoticCoyote writes "
I've just posted a short review of GCC 4.0, which compares it against GCC 3.4.3 on Opteron and Pentium 4 systems, using LAME, POV-Ray, the Linux kernel, and SciMark2 as benchmarks. My conclusion:
Is GCC 4.0 better than its predecessors? In terms of raw numbers, the answer is a definite "no". I've tried GCC 4.0 on other programs, with similar results to the tests above, and I won't be recompiling my Gentoo systems with GCC 4.0 in the near future. The GCC 3.4 series still has life in it, and the GCC folk have committed to maintaining it. A 3.4.4 update is pending as I write this.
That said, no one should expect a "point-oh-point-oh" release to deliver the full potential of a product, particularly when it comes to a software system with the complexity of GCC. Version 4.0.0 is laying a foundation for the future, and should be seen as a technological step forward with new internal architectures and the addition of Fortran 95. If you compile a great deal of C++, you'll want to investigate GCC 4.0.
Keep an eye on 4.0. Like a baby, we won't really appreciate its value until it's matured a bit.
"
I'll tell you what the problem is... (Score:5, Funny)
Or you could wait to compile 4.0 until the 3.0 branch makes it to 3.9.9, then it will be close enough anyway. YMMV, people say I give out bad advice, go figure...
I got your value (Score:4, Funny)
Does this mean I have to wait until it's 18?
We have this thing on Earth, called tact. (Score:4, Funny)
Is that what you say to new parents? :-)
Screenshots? (Score:5, Funny)
Re:I got your value (Score:5, Funny)
Re:The performance of compiled code (Score:5, Funny)
You work at Microsoft, right? No? Intel?
Re:The Future? (Score:5, Funny)
The value of a baby (Score:5, Funny)
Seriously, this is why I don't appreciate babies. At least after about 4 or 5 years, they're useful for mild manual labour. Sure they'll complain and cry, but all you gotta do is tie their dishwashing to the number of fish heads they're allotted that week. Works pretty well, I gotta say. Anyway, at least they're not a net productivity drain like babies are.
Anyway, what I mean to say is: from your description, it looks like I'll be staying away from GCC 4 for a while, too. Goddamn babies.
-Laxitive
The ? operator (Score:5, Funny)
Re:I'll tell you what the problem is... (Score:4, Funny)
V3-V1~2(V3-V2)
where V1 was used to compile V2, and V2 was used to compile V3.
Like a baby (Score:4, Funny)
"Come here son. Did you know your mother and I almost decided to not keep you when you were born? You were just a baby at the time, you didn't seem to have any value. I mean, seriously, what use is there for a baby? I'm glad we didn't make that mistake.
Now go play outside and don't come back before dinner time, and pick up the trash when you leave."
Any big spoilers in the review? (Score:4, Funny)
"Like a baby..." (Score:5, Funny)
Are you kidding? Babies are worth $15,000-$20,000 easily, even if they're female. Once e-Bay stops being a bunch of pussies and we get some open bidding started, I expect their value to go up even higher.
Once again, we see that the
Re:Expected (Score:5, Funny)
Re:The performance of compiled code (Score:1, Funny)
But, noooo. Pclminion claims that if I spend another two hours I can get an extra 500%. So I'll bring it down to 2 seconds. And then, I can spend another 2 hours and get another 500% speed up and get it done to 0.4 secs. According to this logic I can optimize everything to run in instant time.
Re:The performance of compiled code (Score:3, Funny)
Gentoo? Crash? No way, dude. It, like, never crashSegmentation fault.
Re:Expected (Score:3, Funny)
Users?? (Score:5, Funny)
Re:The performance of compiled code (Score:5, Funny)
Re:The ? operator (Score:5, Funny)
In case you were wondering why anyone would want to use a=min(a,b), you really haven't programmed enough. To take a simplistic example, how would you find the largest integer in an array? (Sure, you can just #include , then say *max_element(a,a+N) and be done with it, but let's suppose you don't want to do that...)
Well, the way to do it would be to write a loop like this: I really think it's faster and better to code the last line as largest>?=a[i]. There is less unnecessary clutter.
Oh well. I guess this comment will now lose all its Funny mod points, but what the heck.
No danger (Score:3, Funny)
Oh well. I guess this comment will now lose all its Funny mod points, but what the heck.
To the contray, now it's even funnier.
Re:The performance of compiled code (Score:3, Funny)
Aramathea. He who is valiant and pure of spirit may find the
Holy Grail in the Castle of Segmentation Fault'.
ARTHUR: What?
MAYNARD: '... the Castle of Segmentation Fault'.
BEDEVERE: What is that?
MAYNARD: He must have crashed while carving it.
LAUNCELOT: Oh, come on!
MAYNARD: Well, that's what it says.
ARTHUR: Look, if he was crashing, he wouldn't bother to send it over the network
'aaggggh'. He'd just print it!
MAYNARD: Well, that's what's his comment says
GALAHAD: Perhaps he was dictating.
Re:The ? operator (Score:5, Funny)
That's because they were conflicting with the new gphp front-end.
Re:I'll tell you what the problem is... (Score:1, Funny)
gcc40_by34 = gcc34.compile(gcc40.src());
gcc34_by40 = gcc40_by34.compile(gcc34.src());
gcc40_by34_by40 = gcc34_by40.compile(gcc40.src());
gcc40_taintfree = gcc40_by34_by40.compile(gcc40.src());
Then its just a series of compiles to apply the antitaint.
Everybody knows that!