Examining the User-Reported Issues With Upgrading From GCC 4.7 To 4.8

Posted by samzenpus on Monday January 20, 2014 @04:52AM from the making-it-better dept.

Nerval's Lobster writes "Developer and editor Jeff Cogswell writes: 'When I set out to review how different compilers generate possibly different assembly code (specifically for vectorized and multicore code), I noticed a possible anomaly when comparing two recent versions of the g++ compiler, 4.7 and 4.8. When I mentioned my concerns, at least one user commented that he also had a codebase that ran fine after compiling with 4.6 and 4.7, but not with 4.8.' So he decided to explore the difference and see if there was a problem between 4.7 and 4.8.1, and found a number of issues, most related to optimization. Does this mean 4.8 is flawed, or that you shouldn't use it? 'Not at all,' he concluded. 'You can certainly use 4.8,' provided you keep in mind the occasional bug in the system."

3 of 148 comments (clear)

Min score:

Reason:

Sort:

Re:Use it, sure - it's not a bug, it's a feature by QRDeNameland · 2014-01-20 05:44 · Score: 5, Funny

Obligatory XKCD

--
Momentarily, the need for the construction of new light will no longer exist.
Re:Keep in mind the occasional bug in the system? by gl4ss · 2014-01-20 05:54 · Score: 3, Funny

obviously you're not an ex-symbian developer!

--
world was created 5 seconds before this post as it is.
Re:Use it, sure - it's not a bug, it's a feature by fahrbot-bot · 2014-01-20 07:43 · Score: 3, Funny

Obligatory XKCD

That has got to be one of the most dead-on appropriate "obligatories" I've seen in a long time.
For sure. Even as a long, long time Emacs user, I didn't know you could program it for that.

--
It must have been something you assimilated. . . .