Linked by David Adams on Mon 5th Mar 2012 22:45 UTC, submitted by gogothebee
Hardware, Embedded Systems "After struggling with this issue for well over a year and really pushing hard to track it down in the last two months I was finally able to come up with a test case running 'cc1' from gcc-4.4 in a loop and get it to fail in less than 60 seconds. Prior to finding this case it would take anywhere up to 2 days with 48 cores fully loaded to reproduce the failure. AMD confirms. ' isn't every day that a guy like me gets to find an honest-to-god hardware bug in a major cpu!'"
Thread beginning with comment 509667
To read all comments associated with this story, please click here.
good behavior from their side
by wanker90210 on Tue 6th Mar 2012 10:40 UTC
Member since:

AMD working on fixing the bug instead of covering it up makes me like the company even more.

Reply Score: 3