Originally Posted by KyadCK
Awww, you're one of those people who rates Prime higher then AMD's own testing and binning, aren't you? People like you are so cute, I wish we could put you next to the puppies in the window of pet stores.
In all seriousness, If you had any idea what those CPUs have to go through to be considered good enough to sell, you'd crap yourself. AMD, intel, and nvidia are not in the business of selling things that will just be RMAd or don't work. Not to mention this is one of the higher end parts, and if something didn't work AMD could lop off a couple cores that were being problematic and sell it as a lower part, free of charge.
Not to mention those same tests were done across multiple Giga and Asus boards, but if you think this is all happening on just one combination of hardware, be my guest and list it.
I also love how you completely ignore Red's argument and just post whatever was on your mind. You'll fit in just fine here.
Well CK got their first and I don't think I could have said it any better than he did. You in no way answered my question. And if by your own logic, ( P95 is just a set of math problems) then you are saying that every single other load/stress test, and the extensive and intense testing of the binning process would miss "instabilities?'
Thanks for the response, but you really did not address anything in my question which was -what of all of the bug fixes and revisions? If a program is being "bug fixed" and revised for stable support for only Intel, how can you be so sure that it's not an 'unfixed bug' that is the problem here.
(From the P95 Change logs)
27.1 alpha December 5, 2011 Intel AVX support
(32 bit only)
27.2 alpha December 19, 2011 Includes all FFT lengths; first Linux/MPrime test version
27.3 beta February 16, 2012 64 bit AVX support
27.4 beta March 9, 2012
27.6 beta April 24, 2012 Bug fixes;
(v27.5 was skipped; the underlying math libraries went through a revision, but Prime95 was not modified.)
27.7 beta May 3, 2012 More bug fixes
27.7 May 15, 2012 Stable AVX support (for Sandy Bridge and Ivy Bridge CPUs, Core i3/i5/i7-2xxx and 3xxx models)
if it's simply a mathematical equation being presented , then what are all of these "bug fixes?' or FLAWS in the program being fixed? and if it is just a mathematical equation being presented, then why is the program being altered to to fix the operation on one architecture (note 27.7 'stable' AVX support for sandy bridge and ivy bridge CPU's) what then was the purpose of that revision and why was it needed for 'stable ' operation? I do not see a revision for stable operation for Piledriver/Vishera operation.
I said it before that i would not know good or bad code if it bit me on the ***, however how can some be so certain that it's definitely not the program when P95 has through the history needed 'bug fixes' and 'stable operation' fixes to run. Especially on a CPU that has been out for only a few weeks. Like I said I am genuinely interested in the answer. But my question about bug fixes seems to be ignored. It seems that the prevailing attitude by some is that P95 is infallible when it obviously has needed to be modified and fixed over the years to accommodate new designs.
thanks for the reply Rvaughn.Edited by Red1776 - 11/20/12 at 9:54am