Interesting find, Benchmark favs Intel purely based on CPUID...
http://arstechnica.com/reviews/hardware/atom-nano-review.ars/6
http://arstechnica.com/reviews/hardware/atom-nano-review.ars/6
Second, there's the issue of performance when Nano is identified as AuthenticAMD. If performance between the AMD and Intel CPUIDs was identical, there wouldn't really be a story here, but it isn't, and that's curious. Futuremark could plausibly argue that VIA's C3/C7 processors weren't exactly on the radar back in 2004-2005, but AMD and K8 certainly were, and K8 launched with full SSE and SSE2 support, with SSE3 added in 2005.
None of this constitutes proof of wrongdoing, but it flies in the face of Futuremark's neutrality claims. Bad code is a fact of life, but companies that write benchmarks for a living and sell those benchmarks as evaluation tools have a responsibility to ensure that their software delivers the neutral framework that it promises. Based on the information I've gathered thus far, it seems Futuremark may have created three paths—one for Intel, one for AMD, and one generic "other" path. There's nothing wrong with optimized code paths, but our results would seem to indicate that some paths are decidedly more optimized than others.
The graph above covers all of PCMark 2005's test suites except for the memory benchmark. As you can see, everything here is as it should be; PCMark doesn't care if Nano identifies itself as GenuineIntel or CentaurHauls. Memory subsystem performance, on the other hand, looks a wee bit different.