pigeon768 wrote:-march=core2 -mtune=generic is counter productive. Use -march=native.
Either way, the atom is i686. The fit-pc1 had a i586 geode, so that's why the article says to use i586 CHOST.
The atom, indeed, is i686, so i686 CHOST should be used.
But, since gcc doesn't yet know the atom scheduling it's better to give a hint about the scheduling, thats the -mtune switch for. And if you want to use distcc for compiling, which i do, you will have to specify the correct arch including supported extensions, otherwise (with -march=native) distcc won't compile remotely but only local.
In general, the atom supports the extensions the core2 supports too, so nothing done wrong with this choice.