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

 



Forgot your password?
typodupeerror
Get HideMyAss! VPN, PC Mag's Top 10 VPNs of 2016 for 55% off for a Limited Time ×

Submission + - Examining the User-Reported Issues with Upgrading from GCC 4.7 to 4.8 (slashdot.org)

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. Take a look at how he reached his results.
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Examining the User-Reported Issues with Upgrading from GCC 4.7 to 4.8

Comments Filter:

Time-sharing is the junk-mail part of the computer business. -- H.R.J. Grosch (attributed)

Working...