Quote Originally Posted by kill_a_wat View Post
Seems like some people are having problems with Bloomfield and GFLOPS in Linx and some aren't...so perhaps it's another problem?
Have you checked other benchmark results?
LinX/y-cruncher seems to count on some cycle-based timers, which might cause wrong execution time and thus wrong GFlops.
You could try y-cruncher, which run-to-run delivers a more stable peformance than LinX.
(and count realworld time against the reported execution time)

Quote Originally Posted by Leeghoofd View Post
I clocked the 980X up to 4Ghz (sample needs a whopping 1.4Vcore lol) and got 57-58Gflops §6GB 1600C8 on Win7 64), I see Gautam with 980X at 4.7 having only 51Gflops...
It seems that LinX doesn't scale (well) with 6-cores.
So it might result in a very unstable GFlops because of resource contention, etc.